I have ADHD. I also run 26 microservices on a single RTX 4070.
These two facts fight each other constantly.
The Problem
Every ADHD developer knows this cycle:
- Start exciting new project
- Hyperfocus for 6 hours
- Ship something half-finished
- Context switch to next shiny thing
- Forget what you built yesterday
I had 60+ projects in various states of "almost done."
The Fix: Structured Missions
I stopped reading documentation. Instead, I built follow-along missions where each step bypasses the executive function gate.
Not "learn about Docker networking." But "run this one command and see if port 5027 responds."
The 7 Builds That Stuck
- CDP Browser Automation — one Python script, one WebSocket connection
- Local AI Mesh — multiple Ollama models coordinating on one machine
- ComfyUI + Ollama on 8GB VRAM — image gen AND language models without crashing
- Web-to-APK in 10 Minutes — any web tool becomes an Android app
- AI Manga Pipeline — story beats to assembled pages, all local
- Self-Hosted Stack — tools that survive vendor churn
- Orchestration Patterns — cron jobs, health checks, daemons
Why This Works for ADHD
Each build is:
- Time-boxed: 45-90 minutes
- Dopamine-rewarding: output immediately
- Externalized: no planning in your head
- Completable: starts and finishes in one session
- Stackable: each feeds the next
The Architecture That Emerged
After all 7, I had 26 microservices running. Not because I planned them. Because each mission built one thing, and they naturally connected.
That's the ADHD advantage: we don't plan cathedrals. We stack interesting bricks. Sometimes a cathedral appears.
The full set of 7 missions with configs and video walkthroughs: AI Creator's Toolkit
Questions welcome.
Top comments (0)