Incident Response Best Practices for Solo Dev Teams
A practical guide to incident response best practices for solo devs and indie teams: what to build, what to skip, and how to not get paged at 3 AM for nothing.
Journal
-
-
Cyclomatic Complexity: What to Build or Refactor Next
Your codebase's complexity scores tell you exactly where to start and what to fix before you build anything new.
-
AI Software Engineering in 2026: What Actually Changed
Which AI tools actually change your output in 2026, where AI-generated code breaks silently, and what the shift means for your day-to-day engineering workflow.
-
AI Pair Programming: What Actually Works for Solo Devs
AI pair programming in 2026 means choosing between autocomplete, context-aware editors, and agentic tools. Here's the workflow that actually holds.
-
Build an AI Action Items Extractor: What It Actually Takes
What it really takes to build an AI action items extractor as a weekend project: the stack, the cost, and who'd actually pay for it.
-
Code Refactoring Techniques That Actually Ship Clean Code
The code refactoring techniques worth knowing: extract method, composing, branch-by-abstraction, and the signals that tell you when to use each one.
