Add daily emails and archive
This commit is contained in:
parent
7ec664a810
commit
e2b6832598
379 changed files with 11132 additions and 0 deletions
25
source/_daily_emails/2023-09-21.md
Normal file
25
source/_daily_emails/2023-09-21.md
Normal file
|
@ -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.
|
Loading…
Add table
Add a link
Reference in a new issue