The canonical Boolean values in FORTH are 0 and -1 (that is, all bits set). IIRC the point of that is to unify the bitwise and logical operators, though, not detect bitflips.

Also, at the machine code level, a Boolean controlling a branch or a while loop often doesn't ever make it out of the flags register, where it'll only be a single bit anyway because that's how the hardware works. Not really changeable in software.

There's a new, professionally-published book version of "There Is No Antimemetics Division" out as well[1], if you want to support Sam's work that way. I have print copies of both the self-published V1 and the new V2. I'm very excited about the latter, though I haven't finished it yet.

[1]: https://qntm.org/antimemetics

I don't think it's that the lawyers are undifferentiated; some are better than others, in the same way some real estate agents are better than others (source: people complaining bitterly about theirs).

The problem is that there's currently no effective way to comparison shop. Needing a real estate agent or lawyer is a rare event for most people, so they don't have grounds to make a comparison. And you can't really tell how good they are until you've hired them.

Compare to, say, an auto mechanic. In the US, 90+% of households own a car, and after a few years of car ownership, unless you're a much luckier person than I am, you've probably been to a few mechanics and had some good and bad experiences. On top of that, most of your friends have done the same, so it's much easier to get enough data to figure out who to take your car to next. And, of course, the stakes are a bit lower: a lot would have to go wrong for you to end up in jail because you picked a bad mechanic, and cars are usually cheaper than houses.

Good to know! At previous jobs, that information wasn't available to me (and it didn't matter because the customer bases were small enough that every customer was top priority), so I assumed it was considered more sensitive than it perhaps is.

Tangential, but I wonder if the given example might be straying a step too far? Normally we want to keep sensitive data out of logs, but the example includes a user.lifetime_value_cents field. I'd want to have a chat with the rest of the business before sticking something like that in logs.