Conceptual, architectural explainers — how a subsystem actually works underneath.
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.
How IBM's rushed 5150 became a cloneable platform—and why published interfaces, an independent BIOS, and DOS all mattered.
How transistors, integrated circuits, memory, displays, batteries, and manufacturing—not one magic chip—made personal computing portable.
How Windows uses hardware virtualization to carve out a memory region even a compromised kernel can't touch, protecting credentials from pass-the-hash attacks.
The high-performance, always-available kernel tracing infrastructure that nearly every serious Windows diagnostic and monitoring tool is actually built on.
The layered, extensible packet-filtering architecture in Windows that both Windows Firewall and most third-party security software build on.
Why Windows services stopped interacting with the desktop starting with Vista, and what changed in the session architecture to cause that.