Conceptual, architectural explainers - how a subsystem actually works underneath.
How rollback netcode predicts remote inputs, restores deterministic state, re-simulates missed frames, detects desyncs, and balances delay with artifacts.
How cartridge dumpers read ROM, mapper banks, save memory, and metadata-and how repeated reads, hashes, provenance, and safe handling establish confidence.
How emulators serialize CPU, memory, devices, clocks, and pending events-and why completeness, determinism, versioning, and validation matter.
Ctrl-Z, bg, fg, and a trailing & all touch one mechanism: process groups and Unix signals deciding which process can read your terminal.
Bash, Zsh, and sh accept most of the same commands, which is exactly what makes their real differences easy to miss until a script breaks.
A colorful prompt showing git branch and exit code is not a separate program - it is a string the shell re-evaluates before every command.
An unquoted variable works in testing, then silently breaks the first time its value contains a space - the single most common shell scripting bug.
Terminal and shell are separate programs linked by a kernel pty: one renders characters and handles input, the other interprets commands.
Full-screen terminal apps like htop and vim redraw the screen selectively and read keystrokes one at a time. This is the library layer that makes it possible.
A forensic account of the dot-com boom, its long collapse, and why real innovation coexisted with prices that outran plausible profits.