Isn't "trunk based development" just a complete crock of shit?
bucket.co
bucket.co
- Whether you're primarily developing or maintaining
- Size and organization of the codebase
- Size of the team working with the codebase
- Your production deployment strategy
- Probably others
Here's the thing: I know teams using trunk-based development and teams using feature branch development, and they all work in the same organization! Like most things in software development, the best strategy for you is dependent upon your needs and you should eschew the idea that there's only one right way to do everything.
And working with like-minded colleagues on ideas such as this, is a very nice thing to have. It is something to seek out when looking for a new role.
Agree 100% and that's on excellent callout.
Indeed, chunking and sequencing changes is a learnable skill, like many other things such as system design, effective unit tests, or writing code that compiles in the first place. Out of those it's not the hardest - it's hardly like learning a new programming language - and it is very beneficial.
But if there are long-lived branches, or a "release branch" which means that main is not what is deployed to production, or that main/"the trunk" is not what is merged onto, then you are definitely not doing trunk based development.
This is a different question to "is this advisable?"
Just because you can do something complex, doesn't mean you should. Avoiding this complexity can be beneficial.
Yes, some of the complexity might show up somewhere else instead. But which place is the best place for it?
Maybe, trunk-based development is the idea that "branching strategies are not the right place to put that complexity".