Runaho

I’ve been writing software since 2015 — mostly in startups, mostly under pressure. I care about performance, security, observability, and maintainability. But what I spend the most time on is thinking about why any of it matters.

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”? #

The name has two roots. Runa — or Rune — comes from Old Norse and Proto-Germanic tradition, where it means hidden knowledge, wisdom carried in symbols, the kind of truth you have to earn. It’s the root of the runic alphabet, and it carries a mythological weight: that some things are revealed only to those who seek them.

Ho comes from Japanese — a suffix meaning one who carries, grows, or brings something to completion. Put together, something like the one who carries ancient wisdom or the keeper of hidden knowledge seeking fullness.

I chose it before I even entered this field. It came from a feeling I couldn’t quite name yet — an obsession with understanding things fully, with not stopping at the surface. Technology was just the medium. The drive was always to learn until nothing was left unasked, and then to pass it on.

That impulse is still what this site is about.