Development Workflow & Best Practices covers practical techniques for building, reviewing, testing, and deploying software efficiently. The articles focus on sustainable workflows, automation, and quality gates that help prevent bugs, reduce technical debt, and keep development predictable as projects grow.
If you’ve been following my previous posts, you know I’m a big advocate for Trunk-Based Development and shrinking your pull requests until they almost feel too small. In a perfect world, developers merge code directly into the main branch multiple…
If you’ve followed the first two parts of this series, you know the hard truth: most teams aren’t actually doing Trunk-Based Development. They are doing “Short-lived Feature Branching” with better branding. We’ve talked about why your PRs are still too…
Most teams don’t realize this, but their biggest bottleneck isn’t architecture, tech stack, or even legacy code. It’s pull requests. If you read about trunk-based development, you’ll see the same advice repeated everywhere: small changes, frequent merges, fast feedback. Sounds…