Member-only story
TDK: Turbo Debug Konsole
Watching Your Program Think in Turbo Vision
Printing is the debugger everyone actually uses. It survives every fashion cycle because it asks nothing of you: no attach, no breakpoints, no ceremony. But printing has a failure mode that gets worse the more interesting your program becomes. The moment output arrives faster than you can read, or two subsystems write at once, or the thing you are watching is a language model streaming markdown a token at a time, the terminal stops being a window into your program and becomes a firehose pointed at your face.
The usual escape is to redirect to a file and read it afterwards. That works, and it also throws away the one property that made printing useful: you were watching it happen. A log file tells you what your program did. It does not let you watch it think.
So I built a second screen for it. A separate process that opens a socket, accepts whatever you stream at it, and renders it in a text-mode UI with windows, menus and scrollback. It is called turbo-debug-console, and the interface is unapologetically 1991: double-line borders, a menu bar, a status line, drop shadows on the windows. That aesthetic choice turns out to be an engineering choice, for reasons worth going into.
