From 853637af94abbce23d4567500410de0bc41a8a33 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Wed, 17 May 2023 22:19:06 +0100 Subject: [PATCH] daily-email: add 2023-05-14 --- src/content/daily-email/2023-05-14.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 src/content/daily-email/2023-05-14.md diff --git a/src/content/daily-email/2023-05-14.md b/src/content/daily-email/2023-05-14.md new file mode 100644 index 000000000..7defa779f --- /dev/null +++ b/src/content/daily-email/2023-05-14.md @@ -0,0 +1,17 @@ +--- +title: > + Releasing small changes often is less risky +pubDate: 2023-05-14 +permalink: > + archive/2023/05/14/releasing-small-changes-often-is-less-risky +tags: + - software-development +--- + +Contrary to what many think (at least to begin with), releasing small, incremental changes often - maybe daily or weekly - is less risky than larger releases containing weeks or months of changes. + +If there is an issue after a large release, diagnosing and fixing it can take longer than a smaller release with fewer changes. + +You might have to revert and roll back to the previous release instead of being able to push a fix for a small change. + +With a small change, the risk of an issue is much lower as it has less chance to impact any other part of the application and is much easier for others to read, understand and debug.