From 311aa22deb0b118bac9934d7a9745502e8ab2c0c Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Sat, 9 Sep 2023 10:45:08 +0100 Subject: [PATCH] daily-email: add 2023-09-04 Charging more _not_ to write tests --- src/content/daily-email/2023-09-04.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 src/content/daily-email/2023-09-04.md diff --git a/src/content/daily-email/2023-09-04.md b/src/content/daily-email/2023-09-04.md new file mode 100644 index 00000000..c355fa9f --- /dev/null +++ b/src/content/daily-email/2023-09-04.md @@ -0,0 +1,22 @@ +--- +title: > + Charging more _not_ to write tests +pubDate: 2023-09-04 +permalink: > + archive/2023/09/04/charging-more-not-to-write-tests +tags: + - automated-testing + - test-driven-development +--- + +Joel Clermont [replied to a previous email on Twitter](https://twitter.com/jclermont/status/1690872089878691840): + +> I once toyed around with the idea of charging MORE to do it without tests. Had a client pushing back very hard when I mentioned testing (what I thought they’d perceive as a benefit). Ended up not pursuing it, but was a fun idea at the time. + +It's an interesting idea. + +How much more would you charge not to write tests? + +How much more would make you feel comfortable and confident that the application works as expected, and would cover the additional time for finding and fixing the bugs caused by not writing tests? + +As Joel said, it was a fun idea, though it seems counter-intuitive to me, as the a client would be paying more for worse software.