[feverishly applauds]

Looks perfect to me!

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.

Thanks for the transcription!

Surely Java can tell the difference between a key with a null value and the absence of that key, no?

I mean, you can set up your deserialization to handle nulls in different ways, but a string to object dictionary would capture this, right?

Because they didn’t want to train their JS developers and didn’t want to cause friction for new projects. They get to say they’re using TS, with basically none of the real advantages. (Apart from general rational error checking.)

[sits quietly in the corner]

Yes, but did you get the job?

Also props for the image description.

Yeah, I’m all about Jetbrains in Night theme. Thanks for the alt text, by the way.

First it needs to work, then it needs to work well, and finally it may or may not work quickly. Along the way, it should also be humorously weird.

Why not ‘i’?

I decided to be wrong because the correct joke would be too convoluted. I’ll work on that implementation and then you can inject it at runtime via reflection.