Hi.
I’m TurboRigby — a developer, system enthusiast, and someone who enjoys understanding why things are the way they are.

I’m interested in systems, runtimes, browsers, and infrastructure more than buzzwords.
I’ve written questionable amounts of low-level and experimental code so I don’t have to believe in magic.

It’ll be a bang as long as it’s written in Golang.

• Operating systems & low-level architecture
• Runtimes, schedulers, memory models
• Browsers (yes, including engines and specs)
• Backend systems that stay boring under load
• Debugging things most people prefer not to touch

I strongly prefer understanding over abstraction and predictability over cleverness.

Frontend is a runtime too — just one with worse constraints.

• Built backend systems where “simple and observable” was the main feature
• Wrote experimental stuff (kernels, languages, runtimes) to remove illusions, not to ship products
• Learned the hard way why large systems look the way they do

Most of my serious work lives outside flashy demos.

• If a system can’t be reasoned about — it’s broken
• If debugging requires faith — it’s already lost
• Complexity must earn its place
• “Rewrite it properly” is usually a trap
• Boring systems scale better than smart ones

I don’t chase hype, trends, or “10x” narratives.
I prefer tools that fail loudly, systems that explain themselves, and code that doesn’t lie.

If something explodes — fine.
At least we’ll know why.

And preferably, it’ll be written in Go.