How geekdojo builds
Developing with AI
Deep dives on how a one-person shop ships like a bigger one — AI agents doing the quality work, a human accountable for every merge, receipts in public repos.
Geekdojo is me, one person. I build Rasputin, a homelab cluster system, and I use AI agents for the quality work a team would normally share: reviewing every pull request for security, writing tests that catch real faults, and fuzzing the parsers. The agents open pull requests; I read and merge each one myself. An agent only stays in the pipeline after it has caught a real problem.
The posts below cover how each piece works, how it broke when I first set it up, and where to find the code. All of it is in public repos. For Rasputin itself, start at the product site, or go straight to the docs, the Learn lessons or the devlog.
Deep dives
How I run a company of one — and it ships like a team
One person, a whole company. The AI system I actually run — engineering, QA, marketing, legal, finance, and the board that runs my attention — every department, in public, with the receipts.
AI wrote the fix. I asked the question that made it right.
A weekly CVE scanner was green on every run it ever made — and had never scanned a single package. The human-AI loop that caught it, killed the broken approach, and shipped the fix in an afternoon.