
Is trunk-based development feasible in a monolith environment?
No, I don't think so. However, not all monoliths are created equal!

Refactoring starts with the first step
Don't even start the mountainous refactoring task yet. Instead, start on something small you know you can do.

Incremental refactoring
All the benefits of working in small batches on a new feature also apply to refactoring.

Do release notes make sense with continuous deployment?
Most likely, only some of your deployments will be worthy of an entry in the release notes. And I think that's perfectly reasonable.

Dismiss stale pull requests when new commits are pushed
Can disabling this feature be a small win for your team?

Feature flags aren't about continuos deployment
Although they do easily overcome a common objection.

Version numbers are free
There is literally an unlimited number of version numbers. Don't be stingy.
Subscribe to the Daily Commit
Every day I write about improving software delivery at small companies like yours. Don't miss out! I will respect your inbox, and honor my privacy policy.Unsure? Browse the archive.

Should we feel bad if we don't deploy on Friday afternoon?
Everytime we decide when to deploy, we're making a business decision. And few business decisions are black-or-white.

What did we change?
What changed in the last month to give us the confidence to deploy at 5pm on a Friday?

Your low standards don't represent an engineering failure on my part
What is it that makes you uncomfortable deploying at 5pm on a Friday? Let's talk about that.