The whole story

The non-traditional route

I took the scenic route to software development. Psychology studies → game design → callcenter → bootcamp → startup burnout → back to school at 33. Not exactly the typical CS path, but it gave me something useful: a systematic approach to understanding why things break and how to build better alternatives.

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

Learning through institutional dysfunction

Then came the education in organizational toxicity. Quality work punished. Systematic 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 building tools that solve these problems systematically.

"I learn to spite those who punish it. If I can suffer and learn and build systems that prevent others from experiencing that dysfunction, then the suffering becomes valuable. If I die with the knowledge, the systems never get built, and the dysfunction repeats."

Current capabilities

What you get when you hire someone who took the long way around:

  • Multi-domain experience: Psychology, game design, cybersecurity, enterprise systems - different contexts, same systematic thinking
  • Problem transformation: Converting institutional trauma into systematic solutions others can use
  • Documentation obsession: Everything captured systematically - enables knowledge transfer without human bottlenecks
  • AI integration expertise: Transparent collaboration that builds capability rather than dependency
  • Local-first philosophy: Privacy-respecting tools that work offline and don't phone home

Recent work highlights

Panopticron - Enterprise Monitoring

Built enterprise-level monitoring system for 6-person agency. Live production system with worker-based data sync, custom visualization, service-oriented architecture. Academic validation through IEEE-formatted report delivered in 16 hours.

Evidence: Live at panopticron.vercel.app

QRY Tool Ecosystem

Local-first developer tools addressing documented problems: context preservation, work visibility, systematic learning, AI collaboration methodology. Each tool solves a specific dysfunction I've experienced and documented.

Evidence: Active development on GitHub

Educational Game Design

Quantum mechanics through dice game mechanics. Complex concepts made accessible without dumbing down. Proven methodology for translating difficult technical topics into intuitive interactive systems.

Evidence: Game development on GitHub

What I'm looking for

Environments where systematic problem-solving is valued over velocity theater. Teams that build solutions rather than just implement predetermined requirements. Organizations that understand the difference between "moving fast" and "building sustainably."

I'm particularly interested in:

  • Developer tools companies - Building tools that make other developers more effective
  • Platform engineering - Infrastructure that enables rather than constrains
  • R&D environments - Systematic exploration of complex problems
  • Educational technology - Making complex concepts accessible without oversimplification

Contact

Want to talk about systematic solutions to documented problems?

[email protected]GitHub →Professional Resume →

Currently finishing graduate degree, available summer 2025