Git’s branching, a power and a menace.

by Jul 7, 2023

Git’s branching, a power and a menace.

More branches? More chaos. The result – sluggish workflows, longer feedback loops, tiresome reviews, late deployments, complex merges.

Following changes across multiple branches – a time stealer, a collaboration killer. Complicated code reviews and merges carry the heaviest toll, hurting code stability and quality.

Delayed integrations? Update release slower, stakeholder frustrations higher, development stalled.

Try to use as few branches as possible, preferably none. Use feature branches for major changes but keep the total count low. This means faster reviews, quicker feedback, smoother deployments.

The golden rule – maintain balance. Wield Git’s branching power, but don’t obstruct feedback, reviews or deployments. Have fewer, but significant branches. This results into better feedback.

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Progressive Enhancement for JS is overrated.

Progressive Enhancement for JS is overrated. In today’s web, HTML + CSS + JS is a package deal. Almost every browser supports the trio, and let’s be real: users expect apps to work smoothly with JavaScript. 95%+ of users have JS enabled – why build for the exception?...

read more

Alpine.js just clicked. 🎯

Alpine.js just clicked. 🎯 Its declarative syntax—attributes on HTML tags—is perfect for simple UI logic. Most of the time, I don’t even need to touch JavaScript. And when I do? I can write just a little bit, and it fits right in. What’s even better? The declarative...

read more

HTMX + ASPNET Core Razor = magic. ✨

HTMX + ASPNET Core Razor = magic. ✨ But HyperScript? Not so much. 😅 As a developer, I gave HyperScript a try for client-side interactions. I really wanted to love it—especially since it’s from the same creator as HTMX. But every time I used it, I spent way too much...

read more