The person is also quite good at specifically putting their words online in a way that others can benefit from them. (Enough so that it’s a bit of a running joke[1] when he quits his job and has time to write some more words.) That skill is generally difficult to transmit, so if they’re saying something in that direction it could be worth listening.
This system seems quite similar to sending messages to oneself on Signal/Telegram/whatever. What I like about using messenger apps is that every note gets a timestamp and that messenger apps are, in my experience, more polished than note-taking apps.
There are screen-locking programs that don't hide what's on the screen (for example `alock` and `xtrlock`). So you can use one of those in a script that also launches this tool.
Good point. Perhaps we could store the length of the common prefix from the last time we went left as well as from the last time we went right. The minimum of those two should remain a common prefix with the search key for the rest of the lookup and should therefore be safe to skip during subsequent comparisons.
But that would actually help it because you can store how far down the match is by that point in the tree, and know how few digits you have to actually compare.
You could quite easily use a t420 keyboard in a t440 with a few pins masked which was the last traditional thinkpad keyboard.
Actually I may be getting the numbers wrong, it could be the t430 that I was thinking about. It's been rather a long time since I did any brain surgery on thinkpads.
> "git oldest-ancestor brancha branchb" does what it says.
The oldest (common) ancestor of two revisions would typically be the initial commit. I assume your alias really finds the last (most recent) common ancestor. But are you aware of the `git merge-base` builtin? Your alias looks an awful lot like it.
...okay, I can let this nonsense go today with very little impact, but if I do... will the team need to deal with it 100 times in the future? (And more broadly, by silence am I contributing to the evolution of a bad engineering culture ruled by poor understandings?)
It is very very difficult to know where to draw the line.
Three axes in my mind to take into account: Likelihood, impact, and complexity. The article seems to mostly be about likelihood and complexity. I'd place more importance on impact and complexity. It's worth saving a headache later if it's simple to do right now, however unlikely it is, as long as it doesn't create a maintenance burden before that point.
