From d891f3e9d19798f769de74156f45512d78b146ac Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Thu, 16 Nov 2023 23:15:16 +0000 Subject: [PATCH] daily-email: add 2023-11-11 Work in small batches --- src/content/daily-email/2023-11-11.md | 28 +++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 src/content/daily-email/2023-11-11.md diff --git a/src/content/daily-email/2023-11-11.md b/src/content/daily-email/2023-11-11.md new file mode 100644 index 000000000..5e2a1381b --- /dev/null +++ b/src/content/daily-email/2023-11-11.md @@ -0,0 +1,28 @@ +--- +title: > + Work in small batches +pubDate: 2023-11-11 +permalink: > + archive/2023/11/11/work-in-small-batches +tags: + - software-development + - git + - continuous-integration + - continuous-delivery + - continuous-deployment + - trunk-based-development +--- + +Software should be designed, written, and deployed in small batches. + +This is the first line from a blog post by Eric Ries and is something that gets discussed with a guest in an upcoming episode of the Beyond Blocks podcast. + +In the post, Eric continues by saying, "Of all of the insights I've contributed to the companies I've worked at over the years, the one I am most proud of is the importance of working in small batches". + +Small batches mean faster feedback, more localised problems as there are fewer changes, and reduced risk and overhead. + +If you work in small batches and make smaller changes, merge them regularly into the mainline branch (ideally, at least once a day), and often deploy changes to production, the releases will be quicker and less stressful, and clients and customers will be happy as their changes will be available sooner. + +I've worked this way, and with long-lived feature branches and large, infrequent deployments, I prefer to work in small batches and deploy often. + +The full blog post is found at .