I think their normal intake was 4 or 5 coffees. I’d expect to feel **something ** cutting down from that to 0. Maybe the decaf placebo really worked for them, most days?

Maybe? I was surprised to hear James saying he hadn’t had any caffeine on multiple days.

One coffee a day? Those are rookie numbers!

Joking aside, that could mean there’s already significant variance in their intake.

You could maybe work this out from a meta analysis of the studies about caffeine and focusing, where the control group is actually just in withdrawal.

I was surprised by the lack of correlation between caffeine intake and sleep quality, but the takeaway, for me, is that if they were specifically looking into that, they’d need to control for other factors. And n=5 is pretty small.

Interesting stuff.

[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?

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.