Also had experiences with (some are back in the old days!)
Signal 1 — My day-to-day work centers around building and maintaining web applications that are expected to behave predictably under real-world constraints. I tend to spend more time reasoning about performance characteristics, failure modes, and long-term maintenance than chasing novelty or surface-level features.
Signal 2 — When I explore new tools or technologies, I usually look upstream: runtimes, compilers, frameworks, and automation systems. I’m less interested in what they promise and more in how they behave under load, how quickly they provide feedback, and where their edges start to show.
Signal 3 — I invest heavily in the systems I use every day. My development environments are intentionally configured and kept consistent across machines, my operating system is deeply customized and documented, and my input devices are tuned rather than tolerated. If a system becomes part of my workflow, I want to be able to understand and control it.
Signal 4 — This isn’t about productivity or optimization as a goal in itself. I simply find it hard to rely on systems I don’t understand. Over time, predictability, clear feedback loops, and correctness matter more to me than convenience or novelty, and most of my engineering decisions follow naturally from that.
See some of my projects below ↓