
Runaho
Software. Philosophy. The space between.
I’m a software developer who builds things and thinks about what they mean.
Since 2015, I’ve been writing code professionally — mostly in C# and .NET, with detours into Go, distributed systems, and cross-platform mobile with MAUI Blazor. But the work that has stuck with me isn’t defined by a language or a stack. It’s defined by the problems it solved and the questions it raised.
How I Think #
I care about software that’s understandable. Not just to machines — to the people who have to maintain it, extend it, or use it without reading a manual.
I’m drawn to the edges: where a technical decision becomes a design decision, where a design decision becomes a philosophical one. Why do we abstract things the way we do? What assumptions are baked into our tools? What does it mean to build something “well”?
These aren’t rhetorical questions. I write about them.
Why “runaho”? #
It started as a username — something I typed into a registration form in my early teens and kept using because it stuck. Over time it became less of a handle and more of a signature. Every commit, every project, every forum post. It’s not a brand. It’s just me, consistently.
When I needed a domain for this site, it was the obvious choice. runaho.dev is where I put things I want to stand behind.
What I've Built
Link management and redirect intelligence platform. Real users, real production.
Privacy-first content moderation tool. High-performance blacklist aggregator and query service.
Adopted by 15+ institutions. Concurrent load, flexible question types, production edge cases.
Deployed for one of the world's largest international organizations. Correctness isn't optional.