Technical
DevOps for Solo Builders: Just Enough Process
The DevOps literature is written for teams of fifty. As a solo builder I do not need half of it. But I also do not get to skip all of it. The question is: what is the minimum I need to ship safely?
My Four Non-Negotiables
Git as the source of truth: every deploy starts from a git commit, never from a local file. If it is not committed, it does not exist. This one rule prevents 'which version is live' confusion entirely.
One command deploy: npm run deploy or make deploy. Never a sequence of steps. The command is a script that runs the steps. When the steps change, the script updates. I do not remember them.
Rollback plan per service: before any deploy, I know how to revert. Vercel has instant rollback. AWS SAM has sam deploy with the previous version tag. WordPress has a backup plugin. No 'hope' in the plan.
Observability at minimum: CloudWatch Logs, Vercel logs, and email alerts on failure. I do not need Datadog as a solo builder, but I need to know within hours when something breaks, not within days.
What I Skip
Blue-green deployments, canary releases, feature flags, staging environments that mirror prod, load tests. Each of these is valuable for bigger teams. For a solo builder the overhead beats the benefit. Vercel preview URLs cover 80% of what a staging environment would.
The Deploy Script
#!/bin/bash
# deploy.sh - minimum viable deploy
set -e
npm run lint
npm run typecheck
npm run test
git push origin main # Vercel deploys on push
echo 'Deployed. Check https://vercel.com/logs'Five lines. Fail fast on lint, typecheck, or tests. Push. The hosting platform handles the rest. I read this script maybe once a month and it has not changed in half a year.
The Mindset
Process is overhead. Overhead compounds. Every minute of DevOps tax I add is a minute not shipping features. But shipping broken features is worse than shipping slowly. The minimum viable DevOps is the line where these costs balance.
See the Twelve-Factor App for the timeless principles. The tools change, the principles do not.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read