Most developers interact with DNS the way most drivers interact with their engine: they know it exists, they know it matters, and when something goes wrong they open the hood and stare at it hoping the problem will announce itself. It rarely does. DNS is the infrastructure layer most solo
Every solo project I run has the same problem at some point: the deploy process is whatever I remember it being. SSH in, pull the latest code, restart the service, hope nothing broke. It works until it doesn't, and it doesn't at the worst possible time.
I spent six weeks building a billing system. Custom invoicing, usage tracking, payment processing, dunning emails. It was clean, well-tested, and exactly what I needed. It was also the single worst allocation of time in my entire solo practice. Stripe Billing does all of it. $0 upfront. 0.7% per
pip is slow. virtualenv is clunky. pyenv is fragile. pipx is fine until it isn't. uv replaces all four with a single Rust binary that installs packages in milliseconds instead of seconds. That's not marketing copy. I timed it. What uv Replaces Before uv, a Python
Every solo builder I know has a database running somewhere. A Mac Mini under a desk, a $5 VPS, a Raspberry Pi in a closet. They've spent weeks building the application on top of it. They've spent zero time thinking about what happens when the disk
WordPress powers 43% of the web. That number gets cited in every CMS comparison as if popularity were a recommendation. It's not. Popularity is inertia. And for a solo builder choosing a publishing platform in 2026, inertia is the enemy of a clean stack. Ghost handles blogging, newsletters,
Every production system fails eventually. The question is whether you find out from your monitoring or from a customer. If you're running a solo builder stack — a Mac Mini in a closet, a couple of Cloudflare Tunnels, a PostgreSQL database, maybe a handful of cron jobs that keep
Most people describe tmux as a way to split your terminal into panes. That undersells it by about 90%. tmux is a session manager, a process supervisor, and a deployment tool disguised as a terminal multiplexer. If you run anything in a terminal that needs to survive closing your laptop
Every macOS machine ships with a task scheduler more capable than cron. It restarts failed jobs, fires missed schedules after sleep, handles stdout logging natively, and doesn't require memorizing five-field time syntax. It's called launchd, and almost nobody outside Apple's own engineering teams uses
I used to run Spotlight for search, Rectangle for window management, Flycut for clipboard history, TextExpander for snippets, and a handful of Automator workflows for scripts. Raycast replaced all five. It's free. That's not a marketing claim. I uninstalled four apps in the same week I
I run my own mail server. Postfix on a VPS, DKIM keys I generated, SPF records I wrote, DMARC policies I set. It delivers transactional emails for my applications and handles the occasional notification pipeline. It works. It took about three full days to get to "works." It
Most solo builder stacks have four or five databases pretending to be necessary. PostgreSQL for relational data, Redis for caching and queues, Elasticsearch for search, Pinecone for embeddings, maybe RabbitMQ for pub/sub. That's five processes to monitor, five sets of credentials, five things that can fail at
tool-review
Cursor wraps AI around your editor. Claude Code wraps your editor around AI. That distinction sounds like semantics until you use both for a month and realize they produce different kinds of work. I've been running both since late 2025. Cursor for frontend projects where I'm
tool-review
ffmpeg does the work of five SaaS subscriptions from a single command line. Video compression, audio extraction, thumbnail generation, format conversion, batch processing. If you're creating any kind of content as a solo builder and you're not using it, you're either overpaying for tools
infrastructure
Most developers interact with DNS the way most drivers interact with their engine: they know it exists, they know it matters, and when something goes wrong they open the hood and stare at it hoping the problem will announce itself. It rarely does. DNS is the infrastructure layer most solo
tool-review
pip is slow. virtualenv is clunky. pyenv is fragile. pipx is fine until it isn't. uv replaces all four with a single Rust binary that installs packages in milliseconds instead of seconds. That's not marketing copy. I timed it. What uv Replaces Before uv, a Python
infrastructure
Every solo builder I know has a database running somewhere. A Mac Mini under a desk, a $5 VPS, a Raspberry Pi in a closet. They've spent weeks building the application on top of it. They've spent zero time thinking about what happens when the disk
tool-review
Nginx makes you configure SSL yourself. Caddy does it automatically, for every domain, with zero lines of certificate configuration. That difference sounds small until you've spent an afternoon debugging expired certs at 2 AM. If you're self-hosting anything on your own hardware, Caddy is the web
ai
Most prompt engineering advice is written for people asking chatbots questions. "Act as an expert." "Think step by step." "Be thorough and careful." These phrases do approximately nothing when you're trying to get an LLM to classify 10,000 support tickets, extract
tool-review
Every macOS machine ships with a task scheduler more capable than cron. It restarts failed jobs, fires missed schedules after sleep, handles stdout logging natively, and doesn't require memorizing five-field time syntax. It's called launchd, and almost nobody outside Apple's own engineering teams uses
tool-review
Cursor wraps AI around your editor. Claude Code wraps your editor around AI. That distinction sounds like semantics until you use both for a month and realize they produce different kinds of work. I've been running both since late 2025. Cursor for frontend projects where I'm
ai
Most conversations about local AI models stay stuck on the same demo: install Ollama, run a chatbot, ask it to write a poem. That's a tech demo, not a tool. The interesting part starts when you stop chatting with local models and start routing work through them. Local
strategy
A solo builder writes a script to pull weekly revenue numbers from Stripe and format them into a spreadsheet. It saves 20 minutes a week. Useful, obviously. Worth writing. But it changes nothing fundamental about how the business operates. Then they write a second script. This one reads that same
strategy
Most solo builders get pricing backwards. They look at what competitors charge, knock off 20%, and try to make up the difference in volume. This feels safe. It is the single fastest way to burn out and go broke at the same time. The math on solo pricing is unforgiving,