Nodes & Interests
The background processes. Not for KPI, but for system stability.
Research, weak signals, buried context
I am unusually good at finding things: missing context, buried documents, weak signals, broken assumptions, and the one thread that makes a messy system legible.
Directness as interface
I tend to be direct because indirect systems leak signal. I would rather name the constraint than decorate around it.
- Gaming: Steam · Factorio · Cities: Skylines · Civilization · Pokemon.
- Pattern taste: factories, cities, civilizations, collections, logistics, feedback loops, and long games.
- Board Games: Strategic tabletop sessions. Logic over luck.
- RimWorld: Stress-testing colony logistics. A sandbox for failure recovery.
- Musical: Hedwig and the Angry Inch.
- TV: Doctor Who · Futurama · Black Mirror · Adventure Time · RuPaul's Drag Race · Big Brother · British and American series in general.
- Why they stick: worlds where rules are visible, hidden, broken, gamed, or rewritten.
- Art: Architecture sketches & digital re-imaginings. Archive in progress.
- Visual: Excalidraw diagrams, ASCII art, dark-themed system schematics.
I read less than I used to. These days I learn by tracing systems: product pages, manuals, forums, datasets, maps, games, docs, conversations, and whatever strange breadcrumb explains the whole thing.
Strategy is the skeleton; empathy is the flesh. Long-termism in action, stealth in execution.