The other day I learned that you can just grep an unmounted filesystem device. It will read the entire disk sequentially like it’s one huuuuge file. And it will reveal everything on that disk… whether a file inode points to it or not.

Used it to recover data from a file I accidentally clobbered with an errant mv command. It’s not reliable, but when you delete a file, it’s usually not truly gone yet… With a little luck, as long as you know a unique snippet that was in it, you can find it again before the space gets something else written there. Don’t even need special recovery tools to do it, just use dd in a for loop to read the disc in chunks that fit in RAM, and grep -a for your data.

I mean, yeah, kind of. In the same way pilots fly planes out of a stubborn sense of pride for knowing what all the flight deck controls do.

An analog clock is just three sets of loading bars with their ends glued together. You can tell geometrically what proportion of each division of time (day, hour, and minute) are spent and what proportion remains. You don’t even need the numbers.

If you need stopwatch-level precision, sure, a digital display is superior. But how often do you need that? Most of what I need clocks for is, “Oh, it’s about a quarter to noon, I have a lunch appointment to get to”.

It is my personal preference to visually intuit that the clock hands are roughly separating the hour into 3/4 spent and 1/4 remaining and use that to know how much time I have left to the hour, rather than read the symbols “42” on the display and manually do the mental gymnastics of “well that’s basically 45, which is three quarters of the way to 60 minutes”.

I’ll admit this benefit is marginal.