About

The scenic route

Psychology studies, game design, callcenter, bootcamp, startup burnout, back to school at 33. Not the typical CS path.

Months out of bootcamp, I was handling enterprise logistics for Maersk as a solo developer. API integrations, German customs systems, client relationships - work that should require a team. That's when I learned the difference between writing code and building systems that actually work.

Learning through dysfunction

Then came the education in organizational toxicity. Quality work punished. Careful thinking labeled as "slowness" while depending on the solutions it produced. The classic double-bind: do it fast or do it right, but somehow also make it perfect.

Instead of just complaining, I documented everything. Patterns, failures, what worked, what didn't. That documentation became the foundation for the tools I build now.

Current work

Building local-first developer tools that solve problems I've documented: context preservation (uroboro), work visibility, AI collaboration methodology. Each tool addresses a specific dysfunction I've experienced.

For the full professional history, see my resume.

How this site works

Most text here was drafted with AI assistance. The ideas and experiences are mine - 5+ years of notes and lived experience. AI helps turn rough thinking into readable prose.

I'm transparent about this because AI makes mistakes, sometimes confidently wrong ones. I catch what I can, but I'm not pretending this is all hand-crafted. The value is in the thinking.

If you spot errors, let me know.