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?

There’s room for preference, I can enjoy a dark roast blend, but they seem to be really leaning into it these days.

Bad? Who’s to say. Specialty coffee is 100% Arabica and Arabica is more expensive to source, so, regardless of preference, I’m surprised by “100% the cheap stuff” marketing.

I think it’s an attempt to introduce apparent differentiation at a low price-point. I’m curious about future developments.

I love acidic specialty coffee that tastes like you squeezed half a lemon into the cup, but I also enjoy bolder, more classically intense coffee.

My main point isn’t so much about people’s different preferences, but the way companies seem to be pushing towards one end of the preference spectrum bit because of its value, but because of the cost and margins.

Sounds like you may want to post to main@rblind.com.

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.)

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.

Would you like a snake to replace your camel?

Self-documenting code, high contrast… Carry on.

I don’t know, at least ‘SetPerformance()’ could throw an argument out of bounds exception.

Perfect! Don’t forget to assert the same exception in all the tests.

I smell a NotImplementedException somewhere.

“Slightly better than gas station coffee.” Living the dream!