According to Wikipedia: TempleOS is a x86-64 bit, non-preemptive multi-tasking, multi-cored, public domain, open source, ring-0-only, single address space, non-networked, PC operating system for recreational programming. The OS runs 8-bit ASCII with graphics in source code and has a 2D and 3D graphics library, which run at 640x480 VGA with 16 colors. Like most modern operating systems, it has keyboard and mouse support. It supports the FAT32 and RedSea file systems (the latter created by Davis) with support for file compression.
Terry suffered from schizophrenia and claimed his design decisions were dictated by God (there are many religious/biblical elements throughout TempleOS).
Not quite 49 years old. Rumor is suicide by train. I've never even played with or downloaded TempleOS, but as a hobbyist just reading about Terry's work has always been inspirational.
Covers routing, dependency management, and testing in a single post.
Three strikes and you refactor.
The Top Starred repositories in Github have been analysed to understand which are the most common whitespace types in different programming languages.
Short history of Vim.
See also this recent article ("A Look at Vim, A Text Editor for the Ages"): https://thenewstack.io/a-look-at-vim-a-text-editor-for-the-ages/
Tristan Hume's commentary on text editors.
Including a C version of her program to calculate the 8th Bernoulli number.
"In a 2D top-down map it is sometimes useful to calculate which areas are visible from a given point. For example you might want to hide what’s not visible from the player’s location, or you might want to know what areas would be lit by a torch."
See also Nicky Case's similar "Sight and Light":
https://ncase.me/sight-and-light/
A hand-crafted CD disk image which boots to a small tron game written in assembly is compressed to a 251 byte self-inflating perl command.
Fitting a website into a single IP dataframe: https://tinysite.adamdrake.com/
I agree with much of this advice on testing.
A postmortem of a bad C book from the 90s.
Scott Wlaschin's talk/slides on "railway oriented programming" as a technique of handling errors and composing functions.
Lots of ways to show git branch graphs.
How to write a very simple (non-optimizing) JIT compiler.
Modeling transistors and logic gates with Unix pipes.
Nicolas Seriot's JSON test suite with results against many existing parsers and a new reference parser written in Swift.
Richard J. Ridel's amazing programmable wooden calculator. Bonus: the conclusion has one of the worst descriptions of Universal Turing Machines and the Halting Problem you've read today.
See it in action in his youtube video: https://www.youtube.com/watch?v=vo8izCKHiF0