Exactly. Imagine the board meeting where somebody has to suggest “maybe we don’t want that many more users.” I was about to type “customers,” but realistically a significant portion of this new load is on free plans.

I’d say the desktop offering is the main thing, but moving further into the cloud could be an interesting move on the subscription journey. Not interesting for me, as a user, but as a concept and an investment for the company.

Lie-to-children. See also “perfect is the enemy of good.”

This was very hard for me to understand, particularly when the simple answer in school that was provided for the benefit of the rest of the class didn’t come with a deeper follow-up, but I now recognize the great value in meeting people where they are.

Sure, it’s:

123 Mulberry '); DROP TABLE Deliveries;--

A good reminder that composition is a useful concept.

I mean, if you want your prints to be asynchronous you’re looking for trouble to begin with.

The previous statement is a joke.

Ah, yes: weaponizing cybersecurity requirements to trick - I mean “motivate” - higher management to do things “right.”

Steam, as mentioned, and an old iMac that I’ve been meaning to dual-boot for a while.

This kind of thing is mostly inevitable, but has an impact on software and game preservation.

There’s a lot to talk about from this point alone, but I’ll be brief: having gone through university courses on processor design and cutting my teeth on fighting people for a single bit in memory, I’m probably a lot more comfortable with that minutia than most; having written my first few lines of C in 10 years to demo a basic memory safety bug just an hour ago, you’re way way ahead of me.

There are different ways to learn and gain experience and each path will train us in different skills. Then we build teams around that diversity.

There’s nothing like having your network go poof and knowing with 100% certainty that it’s your fault and you’re the only one who can fix it.

If you’re interested in learning more about SQL, throwing EXPLAIN at your query and the AI’s version may be really interesting.

I’m usually perfectly happy trusting my ORM, but even then it’s really helpful to dig a little deeper to figure things out, both in development and in production.

I’m inferring based on the deprecation of YEAR(4) and the conversion time window that obviously needs to be updated at some point.