From a85943fd2ec0f2cc48a35426202c09b4ed36a6d4 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Mon, 9 Oct 2023 13:14:53 +0100 Subject: [PATCH] daily-email: add 2023-10-05 Some solutions are good enough --- src/content/daily-email/2023-10-05.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 src/content/daily-email/2023-10-05.md diff --git a/src/content/daily-email/2023-10-05.md b/src/content/daily-email/2023-10-05.md new file mode 100644 index 000000000..7dc094eee --- /dev/null +++ b/src/content/daily-email/2023-10-05.md @@ -0,0 +1,20 @@ +--- +title: > + Some solutions are good enough +pubDate: 2023-10-05 +permalink: > + archive/2023/10/05/some-solutions-are-good-enough +tags: + - software-development + - technical-debt +--- + +Once you have a passing test and you're confident your code works as expected, what do you do next? + +Do you keep refactoring and changing it, or is it good enough? + +Do you need to extract additional classes and methods now, or as the test is passing, do you move on to the next task? + +The main objective is to ship the change and for it to provide value to users, not to have a perfect or "gold-plated" solution. + +Once it's shipped, because you have tests, you can confidently refactor it in the future.