Branching considered harmful
Developers should work on trunk, use a monorepo, and automate deployment
As a company grows in size, it tends to accumulate source code in a variety of repositories and branches. One startup I joined had over 80 repositories — about eight repositories for each developer they employed at the time.
Within these eighty repositories were multiple branches: Develop, QA, integration, deploy, master, and so on. Each developer who owned a project could design their own branching strategy. The most complex of them maintained six different branches and cherry…