I built an AI-augmented development pipeline that starts with a Telegram message on the toilet and ends with a merged, tested PR — no keyboard required. This post walks through five stages of evolution, from copy-pasting into ChatGPT like an animal to running a self-hosted ‘scrum team’ of LLM agents on a NAS in my living room. It’s not the shiniest setup, but it’s mine — and it works.

I find myself with a fresh golden hammer in hand every now and then, only to realize a screw would’ve been better. Following principles blindly doesn’t automatically render ‘better code’—there are always tradeoffs, and managing them is a sign of seniority and actual craftsmanship.

Most software teams are split up by technical layers—backend, frontend, and mobile. This seems logical, but it often creates bottlenecks, delays, and frustration. Mission teams flip the script: cross-functional developers own features end to end, from idea to release. This approach speeds up delivery, builds real ownership, and cuts down on endless handoffs. Too perfect to be true? It demands more upfront effort in communication and shared knowledge, but the payoff is worth it.

My wife needed a candle calculator app. I only know Android. So I used Claude Code to build a native iOS app without writing Swift. 19 days, 3 Apple rejections, and 5 hours of certificate hell later—it’s live, it works, and she’s happy.