I have a kitchen slide rule that I use to scale recipes and do simple conversions. I used it last week when inflating a ball that had a target diameter in centimeters, but measuring the circumference was much easier and my measuring tape was in inches.

We don't even need the term "identity theft". We already have a perfectly good word for than: "fraud".

From the article... Passkeys:

- are generated securely and so can’t be guessed - can’t be phished - are unique for each website you use, so if one website is compromised it doesn’t put your other logins at risk

Watch out for Occam's Hacksaw: Any complex problem can be made to look simple by hacking away enough parts of it as "not essential", saying you'll handle them in version two.

Many filing cabinets in the US are also sized so you can put letter sized folders in one way, or rotate the folders 90 degrees and legal sized folders will fit correctly.

You might want to add the --http0.9 flag to curl, to tell it that getting a response of just "ok" (HTTP 0.9 style, body only without headers) isn't an error.

Grep is from an ed editor command: global (g) to apply a command to all lines that match a regular expression, a regex surrounded by slashes (/), and print (p) to display those lines. Or g/re/p for short. This proved a useful enough operation that they made it a separate command in the early days of Unix.

Yeah! I've heard this many times, but it never sticks in my mind.

The minor difference is that :q! quits without saving but returns zero as the exit code, but :cq quits with a nonzero exit code. Git interprets the nonzero exit code as "editing failed", following the Unix convention that zero means success. If you didn't save the commit message while working on it, :q! will send the empty template back to Git, which Git is smart enough to not commit. But if you accidentally save your work partway through, :q! will still commit the message you wanted to abandon.

That was how I learned to tense my ear muscles -- because I could see they made my glasses shift on my face.

I have a kitchen slide that I use for ratios in recipes. It's an old plastic one from Think Geek.

For example, I usually put 15 grams of coffee with 8 oz of water (please excuse the mixed units). To make a different amount, I align the 1.5 on the top rule with the 8 on the bottom rule to set the ratio. Then each number on the top rule (coffee in grams) matches the scaled value on the bottom rule (water in oz). The 6 on the bottom rule aligns with ~1.1 on the top, meaning I should brew my little six-ounce cup with 11g of coffee. In practice, I do this a lot with bread, but the "baker's percent" convention for writing bread recipes makes it a more complicated example.

Another way to use a kitchen slide rule is when scaling a recipe. Say I want to make 2/3 of a batch of cookies. I line up the 3 on top with the 2 on the bottom. Then for each ingredient, I find the recipe's quantity on top, and read off the scaled quantity on the bottom. This works better with recipes that use weights, to avoid awkward fractions or converting between units so you can subdivide.