From 3d3712772e4ee821094c815e3c05eb36545e3d55 Mon Sep 17 00:00:00 2001
From: Oliver Davies <oliver@oliverdavies.dev>
Date: Mon, 17 Mar 2025 00:18:42 +0000
Subject: [PATCH] Add daily email for 2025-03-05

Feature branching slows delivery
---
 source/_daily_emails/2025-03-05.md | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 source/_daily_emails/2025-03-05.md

diff --git a/source/_daily_emails/2025-03-05.md b/source/_daily_emails/2025-03-05.md
new file mode 100644
index 00000000..9f52bb83
--- /dev/null
+++ b/source/_daily_emails/2025-03-05.md
@@ -0,0 +1,30 @@
+---
+title: Feature branching slows delivery
+date: 2025-03-05
+permalink: daily/2025/03/05/slow
+tags:
+  - software-development
+  - git
+cta: ~
+snippet: |
+  As well as causing merge conflicts, feature branches slow the delivery of new features.
+---
+
+As well as [causing merge conflicts][0], feature branches slow the delivery of new features.
+
+Someone needs to be responsible for merging the branches once they've been reviewed and approved, and any further merges into release branches.
+
+This is typically the Lead Developer on the project, but this person then becomes a bottleneck.
+
+They need to oversee all the branches and merges, and know what needs to be merged and where it needs to be deployed.
+
+This slows down the speed of delivery.
+
+In a trunk-based environment, there's only one branch and everyone can commit and push to it.
+
+And, if you're [doing continuous delivery][1], any changes will be automatically deployed.
+
+No more bottleneck.
+
+[0]: {{site.url}}/daily/2025/02/18/conflicts
+[1]: {{site.url}}/daily/2025/02/17/ci-cd