Blog
Welcome to the Blog.
Why Old Machines Teach Systems Thinking
2026-02-22
Retrocomputing is often framed as nostalgia, but its strongest value is pedagogical. Old machines are small enough that one person can still build an end-to-end mental model: boot path, memory layout, disk behavior, interrupts, drivers, application constraints. That full-stack visibility is rare in modern systems and incredibly useful.
On contemporary platforms, abstraction layers are necessary and good, but they can hide causal chains. When performance regresses or reliability collapses, teams sometimes lack shared intuition about where to look first. Retro environments train that intuition because they force explicit resource reasoning. ... continue
Latency Budgeting on Old Machines
2026-02-22
One gift of old machines is that they make latency visible. You do not need an observability platform to notice when an operation takes too long; your hands tell you immediately. Keyboard echo lags. Menu redraw stutters. Disk access interrupts flow. On constrained hardware, latency is not hidden behind animation. It is a first-class design variable.
Most retro users developed latency budgets without naming them that way. They did not begin with dashboards. They began with tolerance thresholds: if opening a directory takes longer than a second, it feels broken; if screen updates exceed a certain rhythm, confidence drops; if save operations block too long, people fear data loss. This was experiential ergonomics, built from repeated friction. ... continue
When Crystals Drift: Timing Faults in Old Machines
2026-02-22
Vintage hardware failures are often blamed on capacitors, connectors, or corrosion. Those are common and worth checking first. But some of the strangest intermittent bugs come from timing instability: oscillators drifting, marginal clock distribution, and tolerance stacking that only breaks under specific thermal or electrical conditions.
Timing faults are difficult because symptoms appear far away from cause: ... continue
Recapping a Vintage Mainboard
2026-02-22
Recapping is one of those maintenance tasks that seems simple from a distance and unforgiving in practice. “Replace old capacitors” sounds straightforward until you are diagnosing intermittent instability on a thirty-year-old board with unknown service history, lifted pads, and undocumented revisions.
Done well, recapping is not a parts swap. It is a controlled restoration process with verification steps before, during, and after soldering. ... continue
IRQ Maps and the Politics of Slots
2026-02-22
Anyone who built or maintained DOS-era PCs remembers that hardware conflicts were not rare edge cases; they were normal engineering terrain. IRQ lines, DMA channels, and I/O addresses had to be negotiated manually, and each new card could destabilize a previously stable system. This was less like plug-and-play and more like coalition politics in a fragile parliament.
The core constraint was scarcity. Popular sound cards wanted IRQ 5 or 7. Network cards often preferred 10 or 11 on later boards but collided with other devices on mixed systems. Serial ports claimed fixed ranges by convention. Printer ports occupied addresses and IRQs that software still expected. These were not abstract settings. They were finite shared resources, and two devices claiming the same line could produce failures that looked random until you mapped the whole system. ... continue