From d17adcacd9144fc9d396ede44bbe0f1929c94a67 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Tue, 16 Jan 2024 23:54:14 +0000 Subject: [PATCH] Add daily email for 2024-01-16 Daily or quarterly? --- source/_daily_emails/2024-01-16.md | 35 ++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 source/_daily_emails/2024-01-16.md diff --git a/source/_daily_emails/2024-01-16.md b/source/_daily_emails/2024-01-16.md new file mode 100644 index 00000000..b1214e41 --- /dev/null +++ b/source/_daily_emails/2024-01-16.md @@ -0,0 +1,35 @@ +--- +title: Daily or quarterly? +date: 2024-01-16 +permalink: archive/2024/01/16/daily-or-quarterly +snippet: | + What if you could only deploy changes daily or quarterly? Which would you pick? +tags: + - software-development +--- + +Imagine this scenario. + +You have two options on how frequently you can deploy code changes to your application. + +Option 1: Every day. + +Option 2: Once a quarter. + +No more, no less. + +I'd choose daily. + +I much prefer to deploy changes as often as possible rather than waiting. + +I'm much more confident when releasing small changes - even if it's a small refactor, such as changing a variable name or extracting a small helper method. + +It might even seem too small to release. + +But the smaller the release is, the easier it is to find and fix any issues, and knowing that the next release would only be the following day makes it easier to fix forward instead of rolling back a large release with months of changes. + +## Here's the thing + +Whilst it may seem counterintuitive initially, it's much less risky to release small changes often compared to large changes infrequently. + +Which option would you choose?