Felix Orlov
I build software and I think about systems — usually at the same time. This space exists where implementation meets reflection: essays, technical notes, and ideas that don’t belong in a portfolio, a pitch deck, or a résumé.
“The fastest way to understand a system is to try to build it — and watch where it breaks.”
What I Do
I’m an engineer who approaches problems as interconnected systems rather than isolated tasks. Code, interfaces, formats, incentives — I’m interested in how structure shapes behavior, and how small decisions compound at scale.
My work spans frontend and backend development, with a strong focus on architecture, tooling, and internal systems. I care deeply about things like abstraction boundaries, information density, and how software influences the way people think and work.
Good software, to me, is quiet. It reduces cognitive load, enables flow, and stays out of the way once it’s doing its job.
This Space
Words
Long-form writing as a thinking tool. These are not polished opinions, but ideas in motion — attempts to reason through complexity by putting it into language.
Code
Technical explorations, experiments, and architectural notes. Real problems, real constraints, real trade-offs. Including mistakes, dead ends, and the parts that don’t make it into documentation.
Vision
Speculative thinking about where technology could go if we asked better questions. Not predictions. Not hype. Just signals, directions, and alternative frames.
Why This Exists
Most of the internet is optimized for engagement, speed, and surface-level clarity. This space is intentionally slower.
It’s an open notebook — a place for deep work, unfinished ideas, and long arcs of thought. If you’re reading this, I assume you’re curious, patient, and interested in understanding things beneath the interface.
Think of it less as a feed, and more as a garden: something that grows through attention, not constant output.