Published in


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…




Everything connected with Tech & Code. Follow to join our 900K+ monthly readers

Recommended from Medium

Cuspidal Robots: A Deep Dive

Search as you type in Flutter

5/9 Binary tree

So you want to build an API — now what?

How to improve writing skills by atleast 80% as a software engineer

Tutorial: Storing Business dependant environmental variables on the database layer [Rails 4+]

Using Team Topologies to discover and improve reliability qualities

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Ted Spence

Ted Spence

Software development management, focusing on analytics and effective programming techniques.

More from Medium

Better Soft Deletes Using NULL

Effective And Efficient Git Workflows — Part 1.

The different git stages for a typical basic Git workflow.

Clean Code — A practical approach

Drawing: I want to clean code!

Summary of What I learned in Design Pattern: Bridge