From 7a0ee1e3e4e487431c7705505003e3cc999c936e Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Wed, 15 Jan 2025 12:00:00 +0000 Subject: [PATCH] Add daily email for 2025-01-11 Who is your BDFL? --- source/_daily_emails/2025-01-11.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 source/_daily_emails/2025-01-11.md 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.