Fun fact: Kodak had some issues with gelatine that contained too much sulfur back in the 1920s, which ruined a lot of the material they were producing. Happened because the cows have eaten a different type of grass.
This led to Kodak becoming a large cattle farming company too, so they had control over that part.
Side effect of this was the development of faster film.
Film science is completely bonkers.
Ousterhouts book was very much an eye opener for me when i stumbled over it some years ago.
All those recommendations from the “clean code” corner always felt a tad off to me, but i couldn’t put the finger on it. Then i read this small and nicely written book an suddenly the fog cleared up.
That wallpaper is something. Wow.
Oh wow, people like that really do exist.
Uhm, no. Multiplexing also existed in pure analog times.
Oh wow.
That looks like an overly complicated solution to a problem that doesn’t exist. Synching stuff that is in git? Why not just use… git? Also npm… and the example has an env var named “DB_PASS” in it. You never put passwords in version control.
A philosophy of software design, by John Ousterhout.
Short book with some fresh approaches that i like way more than some of the established ones.
Non-flat roads do exist.
Some nice ideas in there.
Only the “markdownquote” thing is kinda pointless, especially since they mention it’s mainly used in vim. Because vim can do exactly that already without the need of an external script. Do ctrl+v, mark the lines you want, press “I” (capital i), insert the desired thing, press esc and voila… all the selected lines are now prepended with the desired thing.
edited to make my comment sound less harsh: Nothing wrong with building your own solution if that feels better to oneself though :-)