From 71c8c93f37af655aa03536331fe6a55898329cb3 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Wed, 21 Jun 2023 00:08:42 +0100 Subject: [PATCH] daily-email: add 2023-06-16 Make the change easy, then make the easy change --- src/content/daily-email/2023-06-16.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 src/content/daily-email/2023-06-16.md diff --git a/src/content/daily-email/2023-06-16.md b/src/content/daily-email/2023-06-16.md new file mode 100644 index 000000000..3fb119621 --- /dev/null +++ b/src/content/daily-email/2023-06-16.md @@ -0,0 +1,20 @@ +--- +title: > + Make the change easy, then make the easy change +pubDate: 2023-06-16 +permalink: > + archive/2023/06/16/make-the-easy-change +tags: [] +--- + +Have you worked on some code, whether it's to add or extend functionality or fix a bug and thought, "This would be much easier if..."? + +A quote by Kent Beck: + +> For each desired change, make the change easy (warning: this may be hard), then make the easy change + +If you can refactor the code and make it easier to implement your required change, do so. + +Any automated tests should be passing before and after, and I'd commit the refactored code to ensure any CI pipelines and checks are still passing. + +Then, go ahead and make the required change - add the feature or fix the bug - which should now be easy.