![](https://rblind.com/pictrs/image/65dca91c-dc2f-4373-ab2d-3e7ce631e80f.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
It’s a very different vibe. I remember my first seg fault in C - kids days are missing out!
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.
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.
I’m pretty happy I never got around to RMAing my Zotac graphics card for its whiny fan.
Steve mentions “server configuration,” but I can’t even imagine what that would be.
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?
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!
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.
Or “How Signal is closer in functionality to WhatsApp by the day, because it turns out people like the functionality of WhatsApp.”
Self-documenting code, high contrast… Carry on.
I was thinking about how this would happen and I remembered when signing up for services using Google login, I’d always get a list of information the website would have access to, including the name listed under the Google account. When I didn’t consent to that, I went back.
Now, is there a line somewhere between strictly getting a user’s consent and the user having an expectation of privacy? Yes, and they may have landed on the wrong side of it.
Suffice it to say, this is one of the reasons I prefer to sign up with an email address.
Risks that are already described.
The headline does it’s job getting clicks by making it sound like reviewers names may already be public.
Looks perfect to me!