[ Blog ] · 6 Nov 2026 · 7 min read

My Solo Dev Workflow: Tools and Git Setup That Actually Scale

Real solo dev workflow: my Mac setup, Cursor vs VS Code, Git habits, and productivity system that scales from side project to product.

  • Dev Workflow & Tools
  • solo developer workflow tools and git setup

Three years ago, I spent 14 hours debugging a merge conflict that shouldn't have happened. I was switching between three projects, context-switching every 30 minutes, and my Git history looked like someone had smashed the keyboard. That day I realized my workflow wasn't just inefficient - it was actively making my code worse. I've since rebuilt how I work as a solo developer, and the numbers matter: I cut deploy time from 45 minutes to 8, reduced bug-related rollbacks from 2-3 per month to almost zero, and increased the amount of actual deep work from 12 hours per week to 28. This is the exact workflow I use now.

Why Your Workflow Breaks at 10,000 Hours

Solo developers don't suffer from the same workflow pressures as teams, but we suffer from different ones. There's nobody to catch your mistakes, no code review to force you to think clearly, and no standups to keep you accountable. At 2,000 hours into a codebase, a bad habit compounds fast. I've seen solo founders lose entire weekends to refactoring because their Git history became unreadable. I've seen developers burn out because they never protected deep work time. The workflow you use at hour 100 won't work at hour 5,000. You need systems that scale.

The mistake most solo developers make is treating their personal workflow like it's temporary. You skip the branch strategy because you're the only one reading the code. You commit without messages because you remember what you changed. You skip code review because 'what's the point.' Then at 3,000 hours, your brain doesn't fit the codebase anymore, you can't onboard anyone to help, and you're stuck maintaining your own technical debt. I learned this the hard way. Now I enforce the same discipline on myself that a team would enforce on me.

Cursor Over VS Code: The $20 Monthly Shift That Stuck

I switched to Cursor eight months ago, and I'll be honest: I was skeptical. VS Code was free, familiar, and I'd customized it over five years. Paying 20 dollars a month felt like indulgence. The first week I barely used the AI features. By week three, I was using Cursor's tab autocomplete on 60% of new code. By month two, I was using Cursor Composer (the multi-file refactoring tool) to rewrite entire modules, and I was 35% faster at boilerplate. That's not a guess. I tracked it.

What actually changed: I stopped thinking of Cursor as 'VS Code with AI sprinkled on top.' It's a different tool. Tab autocomplete isn't just faster typing - it's faster thinking. When Cursor suggests the next line of a function, 70% of the time it's what I would have written anyway, which means I'm validating my own logic instead of typing it. That's cognitive compression. Composer is the bigger win: instead of manually refactoring a 300-line module across five files, I describe what I want and it does the plumbing. I review and tweak, then commit. That task used to take me 3 hours. Now it takes 45 minutes. Scale that across a year of refactors and I've gained 80+ hours of actual development time.

The $240 annual cost pays for itself the first month if you're doing any real refactoring. I still use VS Code for quick config file edits or when I'm on a low-battery laptop, but Cursor is my daily driver now. The keybindings are identical to VS Code, and all my extensions work. The switching cost is zero. If you're a solo developer billing by the hour or working on your own product where time is your most scarce resource, this is worth the experiment.

Git Workflow for Solo Developers: Branches and Discipline

This is where discipline actually matters. Here's my structure: main branch is always deployable. Every feature or fix gets its own branch named feature/description-of-work or fix/description. I never commit directly to main. I use conventional commits: 'feat: add export to CSV', 'fix: resolve race condition in auth', 'refactor: simplify payment validation.' That's it. No novel-length messages, but enough to scan the history in three seconds.

I push to a private GitHub repo even though I'm working alone. This serves two purposes: it's my backup, and it forces me to write pull request descriptions. I don't merge until I've opened a PR against main, written a paragraph about what changed and why, and reviewed my own diff. This sounds slow. It saves me hours per month. I've caught my own architectural mistakes in the PR review step, before they became 8-hour debugging sessions. I've documented why deprecated code is there, so I don't rip out something I needed three months later.

The Git discipline forces a question at commit time: does this change make sense as a unit? If I'm fixing a bug and refactoring, those are two commits. If I'm adding a feature and cleaning up unrelated code, those are two branches that I can deploy independently. This matters when a feature is half-done and a critical bug lands. I can pull main, deploy the urgent fix, and still resume my feature without losing work or merging incomplete code. I do this at least twice a month.

The Mac Setup That Survived Three Years

I work on a 14-inch MacBook Pro with 32GB RAM and 1TB SSD. That's the machine. No external monitor, no fancy setup - just the laptop and a mechanical keyboard. I'm not advocating for that minimalism as some kind of virtue. I'm saying it works for me because I optimize for portability over everything else. I can pack up and work from a cafe, the office, or a flight within 30 seconds. I've lost enough time fighting with docking stations and external displays that the trade-off feels worth it.

On the software side: Homebrew manages everything (Node, Python, PostgreSQL, Redis). iTerm2 is my terminal with the Catppuccin theme, but any terminal works. I have a startup script that runs on boot to start the services I always need and mount my cloud storage. GitHub Desktop handles the UI (I know Git CLI exists, but I like seeing my diffs visually). Slack, Discord, and 1Password run in the background. I don't use the trendy productivity apps - no Notion, no Obsidian. I use plain text files in iCloud for notes and a simple Markdown file for my daily stand-in (time log, blockers, wins). That's genuinely it.

The reason this setup lasts is that I didn't optimize for the setup itself. I optimized for the work. The setup is almost invisible. I don't spend time maintaining it, tweaking it, or justifying it. I updated the OS once a year, Homebrew packages once a week via cron. That's the entire maintenance tax. I watch developers spend 20 hours a year fiddling with config files and never ship anything. I spend 2 hours a year on setup and that frees up mental space for actual work.

Staying Focused Without Burning Out

This is the part nobody talks about. Your workflow either prevents burnout or accelerates it. I protect deep work time ferociously. From 6am to 11am, nothing is scheduled. No meetings, no Slack, no email. Phone is silent. That's five hours of uninterrupted coding time. I've done this for two years and my output in those hours is 10x the output of distracted hours. One deep work morning is worth two distracted afternoons.

I close the laptop at 2pm most days. Not because I have some wellness mandate - I don't. Because after two deep work sessions (morning and early afternoon), I'm tired and the code quality drops. I don't push to production when I'm tired. I use the evening for admin work, support responses, or light reading. I work four days per week. Friday is completely off. That's not some ideal - it's the structure that keeps me sustainable at 45 hours per week and keeps the output high enough that I'm not constantly stressed.

The workflow makes this sustainable. Because my Git history is clean, my deploys are quick, and my code is reviewed by myself before commit, I don't have those surprise 11pm debugging sessions that kill your sleep. Because Cursor handles boilerplate, I'm not spending energy on repetitive work. Because I've invested in discipline, the actual coding is the fun part, not the firefighting.

If you're a solo developer, your workflow is your competitive advantage. Invest in it now, before 3,000 hours of technical debt makes it urgent. Start with Git discipline and one tool (Cursor or VS Code, doesn't matter). Then protect your deep work time. Do that for 30 days and measure the difference. I think you'll be surprised.

Building something similar?