diff --git a/source/_daily_emails/2025-01-11.md b/source/_daily_emails/2025-01-11.md
new file mode 100644
index 00000000..8ffc9278
--- /dev/null
+++ b/source/_daily_emails/2025-01-11.md
@@ -0,0 +1,24 @@
+---
+title: Who is your BDFL?
+date: 2025-01-11
+permalink: daily/2025/01/11/bdfl
+tags:
+  - software-development
+cta: ~
+snippet: |
+  Most open source projects have a BDFL who makes the ultimate decisions for the project. Who is the BDFL in your codebase?
+---
+
+Most open source projects have a BDFL (Benevolent dictator for life) who makes the ultimate decisions for the project.
+
+The ones who spring to mind are Dries, Fabien and Taylor for Drupal, Symfony and Laravel respectively.
+
+But what about your codebase?
+
+Who is the BDFL for your application?
+
+Who decides how features should be implemented or what standards to follow?
+
+Who ensures the codebase is consistent regardless of the feature being delivered or the file being read?
+
+If you don't have one, you should.