I’m interested in how systems influence us and how we adapt or push back. That curiosity shows up whether I’m writing fiction, breaking down a codebase, or thinking about how media shapes behavior.
To me, software engineering and storytelling aren’t opposites. Both are their own type of art rooted in constraints, tradeoffs, and designing experiences that make sense to humans. Paradox Inversion is where those interests overlap.
Short stories and serialized work, often speculative, focused on identity, power, technology, and unintended consequences.
Thoughtful takes on software, games, internet culture, and the social impact of technology—less hot takes, more synthesis.
Hands-on software engineering guides focused on real-world problem solving, maintainable systems, and understanding why things work, not just how.
By trade, I’m a software engineer with experience building and maintaining production systems. I’ve worked across the stack and enjoy untangling messy problems—technical or conceptual.
Alongside that, I’ve spent years writing fiction and essays, often circling the same questions from different angles: agency, structure, and the tension between creativity and constraint.
I try to stick to following values when I create:
Clarity over cleverness — In code and writing, I value things that can be understood and maintained.
Technology is cultural — Tools are never neutral; they shape behavior and values.
Learning is iterative — Mastery comes from feedback, mistakes, and reflection, not just tutorials.
Depth beats speed — I’m more interested in lasting ideas than fast content.
When I’m not writing or coding, I’m usually thinking about games (or playing them), listening to music (or creating some), or pulling apart why something works the way it does. This site is a record of that ongoing process.