If C is so great, why do you have to hack in garbage collection?

I bought some of the Star Trek branded wines a few years back. They were unremarkable.

This just blew my mind. I had always assumed Java was older. I started writing hobby projects in Java in the 90s. I don’t think I heard about Python until the early 2000s.

“why” is a perfectly valid question to ask

https://en.m.wikipedia.org/wiki/XY_problem

C++ has had the same style of obtuse errors for decades. They can be a real pain to figure out even if you are used to seeing them.

Nobody reading about the contest in the linked page should have to rely on Google to fully understand the parameters of the contest. Whoever authored this page is lazy.

What do you mean by UTC only?

I was able to read the article without logging in

Check your employment contract. If that includes an NDA or a confidentiality agreement, the company may own your design as well as any code produced. Writing the program from scratch a second time may still end up being company property.

Given that they didn’t put your program into production, it’s unlikely they would pursue you legally for releasing a new version on your own.

I’ve been a vim user for over a decade and I doubt I’ve spent eight hours configuring it in all that time.

Many years ago, I had forgotten my password to the Sprint websiteb so I could log in and pay my cellular bill. I had to call customer support to resolve this. After verifying my activity, the support agent read me my existing password one letter at a time. While this was alarming, I was amused she had to spell out a somewhat obscene phrase for me. This was maybe 20 years ago and I no longer use Sprint.

Biggest raise was about 12%, when I got bumped up to senior a few years back. Currently searching for a new gig so I’m hoping for a nice bump

Does the existing engine phone home or is that something they’re adding?

What don’t you like about medium?

Ad-Free Results

How are you compensating the search engines you query?

There’s no way this is real. Completely insane.

Yes please. Many times when I add a feature I end up refactoring some of the code first to better accommodate it.

Are there any good strategies for avoiding painful upgrades?

If you’re not already doing so, hold design reviews with your users. Breaking API changes should be communicated early and in a way that makes it clear how the users benefit from the change. If the users don’t benefit, you should reconsider why you’re making changes in the first place.

While this looks like a handy tool, it does make me think shell scripting itself needs a cleaner approach than what we have currently.

Sometimes it’s easier to try a new idea in a new language (e.g. the borrow checker in Rust) rather than trying to shoehorn it into an existing language.