32bitkid

I think it’s also think it’s interesting to consider from the perspective of side-channel attacks/information leaks. For the most part, I think text notes are well just text. But I shutter to think what other metadata, fingerprinting, or background conversations/information could be extracted from a bunch of audio. But maybe I’m just being overly paranoid.

For a while, I was using PC-BASIC to generate audio files for the IBM PCjr cassette interface to do some more diagnostics, for a machine that I had that didn’t have a working disk drive. I don’t even know if there is anything else out there to generate those at this point. PC-BASIC is great!

I’d take it one step further: if `git log`—a hierarchical view of the connection of commits—is the only way you (and your team) interact with commit messages, then yea it’s probably fine.

But, I think the value of commit messages become really apparent once you (or your team) are relying on other visualizations of commit messages like `blame` and `bisect`

Tracking down the introduction of a bug with bisect and resolving to a commit whose message in “minor”, because the person in the past didn’t think this change was important enough to describe intent can quite the temporal foot-gun.

This is the epitome of the sentiment: those interested in the pursuit of “hard truths” are only extrinsically motivated to find fault in others and gleefully “correct” another’s “faulty” self perception. Never intrinsically motivated to better themselves…

Tell me more about how everyone else in the “modern world” is the problem…

Legit question: who, exactly, classifies as “the insane” in this statement?

For the latter I use often use `git stash` for that; stashing off the test case/data, then at each step of the bisect, you can do `git stash apply` (rather than `git stash pop`) to reapply the same changes multiple times.

Before moving on, a quick `git reset —-hard` will get back to a clean flip

Something that took me an embarrassing long time to realize was that North American electrical outlet binding terminals are a combination slotted/Robertson screw head. The Robertson is great.

Klein tools makes combination head tools that engage both, which is fantastic if you are upgrading a bunch of outlets.

If I pay for grammarly, and it plagiarizes an existing work but represents it as an entirely new, independent work and I am unaware of the existing work that is being stolen, who is doing the stealing?

When, exactly, was this period of unbiased/opinion-free event coverage in UK journalism you apparently long for? You rail against “modern journalism” like it’s some kind of recent downhill slide, a by-product of modern political biases, but when was this not the case?

git bisect and got blame are underrated tools, that in my opinion get lost in the conversation about should-you-squash-or-not. They really have diminishing returns when you start squashing huge feature branches into a single commit.

This one is interesting, because if I recall correctly, if you are using the single symbol they more or less mean the same thing. You can do ~~~ or ^^^ and get to the same spot

The difference is in their numerical notion. ~N means go to my Nth first parent. Where ^N means my Nth parent, which is really only valuable/useful on merge commits (Or more specifically octopus merges that merge more than two commits)

This is why ~ and ^ in the single form mean the same thing.

So, in one mental model of the DAG you can think of ^ as horizontal navigation (Right) and ~ as vertical (Down)