I'm an actual boss, and wasting a week is cause for a 30-minute post-mortem, not immediate termination.

I am a lead consultant and depending on the size of the project, I do have a team of less senior consultants who are dotted line reports. If I ever found one of my reports who missed deadlines because they refused to do something as simple as launch Claude (with our $5000 a month allowance a piece) and ask it to debug an issue, yes I would write them up.

There is a direct easy to measure line about the revenue that anyone below me makes the company. My revenue per hour isn’t as exact since I support pre-sales and follow on work.

I don't think this is true. Modulo the sign bit, the "next float" operator is equivalent to the next bitstring or the integer++.

Sure, but that operator can propagate a carry all the way to the most significant bit, so a check for bitwise equality after "strip[ping] few least significant bits" will yield false in some cases. The pathologically worst case for single precision, for example, is illustrated by the value 2.0 (bitwise 0x40000000) and its predecessor, which differ in all bits except the sign.

I've never heard anybody (mis)attribute that to Apple.

I would have, and I work in tech. I'd guess that most people who use iOS have zero idea of what Android can and can't do, because they never use it and probably never will so what's the point of trying to find out.

Seconded. I never knew Android had this—but then again I couldn't care less about what Android can do. There is so much stuff fundamentally off-putting for me about the entire Google ecosystem that I'd never consider switching anyway.

On the contrary, I would take this as evidence that these projects are alive and well - they have people who care enough to try to affect their future trajectory.

> There's zero reason to replace your gloves when switching from dicing green peppers for a salad to picking up raw chicken.

Typo?

No typo. That's the direction that's safe.

It seems you're thinking they're switching back and forth, but that's not what they wrote?

It does, in combination with a pinned nixpkgs commit, which you can find like this:

    ~/repos/nixpkgs$ git log --grep='nodejs.* 24.14.0' -1 origin/master
    commit 9c0e2056b3c16190aafe67e4d29e530fc1f8c7c7
    Merge: d3a4e93b79c9 0873aea2d0da
    Date:   Tue Feb 24 16:53:40 2026 +0000
    
        nodejs_24: 24.13.1 -> 24.14.0 (#493691)
    ~/repos/nixpkgs$ nix eval nixpkgs/9c0e2056b3c16190aafe67e4d29e530fc1f8c7c7#nodejs_24.version
    "24.14.0"
    ~/repos/nixpkgs$

I don't think it's abstract at all. Rub something sharp (anything from a stick to a phonograph needle) on an object and you'll directly transcribe its spatial frequency spectrum into an audio frequency spectrum.

Do you think it's obvious that a chick would understand that connection?

It's not about "understanding" that you or me do when we read a wikipedia article. It's about the mechanisms in the brain that encode things.

"Spatial frequency spectrum" typically refers to visual elements of an object, and has nothing particularly to do with its structure. Entirely smooth surfaces banded in different colors have a "spatial frequency". Extremely irregularly surfaces have no effective spatial frequency. Objects on the same scale as, say, a human head, would have to be "rubbed" at ridiculous high rates (and repeatedly) to even get into a "frequency" range that might include pressure variations that would be considered as a "wave".

I think you're imagining an entirely too limited set of objects.

It's possible to fix this in application code with a Primitive<T> or NoDefault<T> wrapper that acts like a T, except doesn't have a default constructor. Use Primitive<int> wherever you'd use int that it matters (e.g. struct fields), and leaving it uninitialized will be a compiler error.

Yea no. I'm not gonna do that.

That line from TRON: Legacy always gave me a shiver.

Nice article. Finally, something that matters on the front page.