From 82fe15fd013d186912e6043aa1ef9d2ef12e7fc4 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Mon, 25 Sep 2023 21:37:20 +0100 Subject: [PATCH] daily-email: add 2023-09-21 Buggy software causes reputational damage --- src/content/daily-email/2023-09-21.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 src/content/daily-email/2023-09-21.md diff --git a/src/content/daily-email/2023-09-21.md b/src/content/daily-email/2023-09-21.md new file mode 100644 index 00000000..6195e7bc --- /dev/null +++ b/src/content/daily-email/2023-09-21.md @@ -0,0 +1,25 @@ +--- +title: > + Buggy software causes reputational damage +pubDate: 2023-09-21 +permalink: > + archive/2023/09/21/buggy-software-causes-reputational-damage +tags: + - software-development + - automated-testing + - feature-flags + - continuous-integration + - continuous-delivery +--- + +As well as taking longer to fix than locally or in a failed CI pipeline, shipping buggy software to production causes reputational damage. + +If an application goes down or doesn't run as expected, it could get noticed by your customers, clients, or your clients' customers. + +You want your customers and clients to be assured you're writing the correct software based on their needs and requirements, and doing so with as few bugs and issues as possible. + +While there are always bugs in software and occasional unexpected downtime, having these happen regularly can damage your and, if applicable, your client's reputation. + +Therefore, it's in everyone's interest to write high-quality and well-tested software. + +There will be fewer bugs, and by following practices such as feature flags and continuous integration and delivery, they can be fixed faster.