What Is Trunk Based Development? A Solo Dev's Take
Trunk based development means merging small changes to one shared branch every day. Here is how it works, what your CI needs, and when a solo dev should switch.
8 articles in Tech stack decisions.
Trunk based development means merging small changes to one shared branch every day. Here is how it works, what your CI needs, and when a solo dev should switch.
A plain-English answer to what an SLO is, how error budgets work, and how a solo dev can set a realistic reliability target in an afternoon.
SRE explained without the enterprise baggage: SLIs, SLOs, error budgets, and a one-evening setup a solo builder can actually keep running.
What is platform engineering, how it differs from DevOps, what a platform team ships, and when a small team should skip it entirely.
Should you use a monorepo or polyrepo? It depends on whether services share code, who needs access, and your CI tolerance. Here's the practical framework.
Solo builders accumulate technical debt faster than teams. Here is what it is, why it happens, and how to manage it before it blocks your next feature.
Your codebase's complexity scores tell you exactly where to start and what to fix before you build anything new.
The code refactoring techniques worth knowing: extract method, composing, branch-by-abstraction, and the signals that tell you when to use each one.