![](https://rblind.com/pictrs/image/65dca91c-dc2f-4373-ab2d-3e7ce631e80f.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
[flashbacks to the backlog being wiped out because “the client already signed off on the release”]
Opinions are my own. Profile picture description: Black on white pictogram with a D20 showing 20 for a head and a game controller for a body and arms, holding a white cane.
[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?
After loving Prey, I’m now playing Dishonored. So far so good, I like how quickly I was able to get zooming and target highlighting in lore appropriate ways!
Self-documenting code, high contrast… Carry on.
Yes! Hahaha, it’s so good.
Number 2 needs to flick the little switch on the SD card.