You saved me a click, thanks.

Importing esthetic preferences over accessibility tells me a lot about the content…

Right, making it look like you know what you’re doing is a great way to advance to the point where you cause real damage. I’m glad you don’t have to do that, and aren’t getting trampled by the people who do.

Oh, uh. I’m wondering if I laid the irony down too thick. I think the comment you originally replied to is probably correct. I think your questions are typical escape hatches for men to be blameless in any situation. I can imagine you didn’t mean them that way, but that’s what’s usually meant by them.

You’re absolutely right. The most likely scenario is that the person with first-hand knowledge misinterpreted the situation. These poor men and their sensitive feelings…

Irony aside, I’m sure it’s a complex situation with different relevant points to any perspective, but the events as told line up with my own experiences.

I’ve witnessed many of the kinds of situations described here and I think the proposed mechanics adequately explain them.

He grows more powerful by the day…

I can’t watch yet, but I have to know: how angry is Steve?

You need to get out more. I totally get that you would think that’s the case, but only if you’re not exploring parts of the internet outside your bubble. It’s absolutely written.

Sure, but also the broader “join my Patreon to get access to my Discord server” market. It’s actually a pretty clever move, if there’s a market for it (there is) and if it replaces more insidious revenue streams (it won’t).

[feverishly applauds]

It’s a very different vibe. I remember my first seg fault in C - kids days are missing out!

The cool thing to do now is to write it in Rust, only using the standard library.

[checks personal website]

Yes, shame on them!

Measure once, cut 38 times.

Chances are, right? At least it’s the first thing I’d check.

Yes! Hahaha, it’s so good.

Number 2 needs to flick the little switch on the SD card.

[flashbacks to the backlog being wiped out because “the client already signed off on the release”]

Wasn’t there a story about people calling curl devs because of car issues?

For what it’s worth, I’m sure the SQLite devs could help somebody clean up their temp files. They just really shouldn’t have to.

I think we’re fully in agreement here: if the API doesn’t specify how to handle null values, that omission means they’re perfectly valid and expected.

Imagine a delivery company’s van exploding if somebody attempts to ship an empty box. That would be a very poorly built van.

That’s the thing though, isn’t it? The devs on either side are entering into a contract (the API) that addresses this issue, even if by omission. Whoever breaks the contract must rightfully be ejected into the stratosphere.