Trunk Based Development
-
pros
-
When you are just starting up. If you are working on your minimum viable product, then this style is perfect for you. It offers maximum development speed with minimum formality. Since there are no pull requests, developers can deliver new functionality at the speed of light. Just be sure to hire experienced programmers.
-
When you need to iterate quickly. Once you reached the first version of your product and you noticed that your customers want something different, then don't think twice and use this style to pivot into a new direction. You are still in the exploration phase and you need to be able to change your product as fast as possible.
-
When you work mostly with senior developers. If your team consists mainly of senior developers, then you should trust them and let them do their job. This workflow gives them the autonomy that they need and enables them to wield their mastery of their profession. Just give them purpose (tasks to accomplish) and watch how your product grows.
-
-
cons
-
When you run an open-source project. If you are running an open-source project, then Git flow is the better option. You need very strict control over changes and you can't trust contributors. After all, anyone can contribute. Including online trolls.
-
When you have a lot of junior developers. If you hire mostly junior developers, then it's a better idea to tightly control what they are doing. Strict pull requests will help them to to improve their skills and will find potential bugs more quickly.
-
When you have established product or manage large teams. If you already have a prosperous product or manage large teams at a huge enterprise, then Git flow might be a better idea. You want to have strict control over what is happening with a well-established product worth millions of dollars. Probably, application performance and load capabilities are the most important things. That kind of optimization requires very precise changes.
-
Backlinks