From 2df3793251562724aee3a4c7c9630333a93a4875 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Sun, 23 Mar 2025 23:16:43 +0000 Subject: [PATCH] Add daily email for 2025-03-19 No-one is paying us to... --- source/_daily_emails/2025-03-19.md | 33 ++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 source/_daily_emails/2025-03-19.md diff --git a/source/_daily_emails/2025-03-19.md b/source/_daily_emails/2025-03-19.md new file mode 100644 index 000000000..682930c5d --- /dev/null +++ b/source/_daily_emails/2025-03-19.md @@ -0,0 +1,33 @@ +--- +title: No-one is paying us to... +date: 2025-03-19 +permalink: daily/2025/03/19/effective +tags: + - software-development + - automated-testing + - test-driven-development +cta: ~ +snippet: | + What are people not paying you for that you need to do to work effectively? +--- + +A great quote I recently heard whilst watching a conference talk was "No-one is paying us to do _something_, but we need to do it to work effectively". + +This talk was about decoupling, but the same quote could be re-used for various topics. + +A common one is automated tests and test-driven development. + +[Tests aren't a line item][0] that should be billed for separately and clients and customers just want their software to work. + +Generally, they aren't concerned that there are automated tests or whether the tests were written before the code. + +If I need to give an estimate, I always include time to write automated tests. + +It's part of my software development process. + +Whether people know they're paying for me to write automated tests as part or not, I can work more effectively when I have tests and am doing test-driven development. + +Both when writing the code, but also if it needs to be [refactored or changed in the future][1]. + +[0]: {{site.url}}/daily/2025/02/23/line-item +[1]: {{site.url}}/daily/2024/10/20/test-then-refactor