Yeah, I don't see myself using this for Git (where it's very easy to see what you're adding, but not obvious and high-cost if you're missing something), but it's my standard approach for Docker images (where it's easy to tell that something is missing, and low-cost to fix it).
It interactively shows you each change that would be added and lets you decide whether it should be staged or not. Down to the hunk level, so you can partially stage a file if you so choose.
A few years ago I had a Windows box where I pointed XDG_CONFIG_HOME et al to the corresponding-ish Windows paths (AppData subdirectories, mostly) so that the many Linux-derived CLI programs I was using wouldn't clutter up my userdir, and it worked pretty well, though there were a few programs that didn't get the memo. Unfortunately I don't remember which ones they were. Most programs get it right, though!
I don't know what the official policy is, but glibc uses versioned symbols and certainly provides enough ABI backward-compatibility that the Python package ecosystem is able to define a "manylinux" target for prebuilt binaries (against an older version of glibc, natch) that continues to work even as glibc is updated.
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.
One small word of caution if you read the older version first: for what I assume are copyright reasons around using SCP in a professionally-published book, the new published version has had to strip out all the SCP references and change the names of all the characters, but it is otherwise very close to the old one. There are a handful of new scenes and some other small differences, but many pages and chapters are word-for-word identical apart from the aforementioned name changes.
This could just be a me thing, but I found this incredibly distracting after being so used to the old version, and just couldn't manage to enjoy it. Fortunately I bought the old one as well.
I’ve read the older version and really liked it, strange ending and all, and I’ve gifted the new version for X-mas. My xmas wish list is for a 6 episode mini-series funded by the fruit company.
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.
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.
In some companies, this type of information is often very important and very easily available to everyone at all levels of the business to help prioritize and understand customer value. I would not consider it "sensitive" in the same way that e.g. PII would be.
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.
