uuid: - value: eed12ec3-1c34-4165-b66d-62dc0cf3dc76 langcode: - value: en type: - target_id: daily_email target_type: node_type target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7 revision_timestamp: - value: '2025-05-11T09:00:32+00:00' revision_uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 revision_log: { } status: - value: true uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 title: - value: | Buggy software causes reputational damage created: - value: '2023-09-21T00:00:00+00:00' changed: - value: '2025-05-11T09:00:32+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2023/09/21/buggy-software-causes-reputational-damage langcode: en body: - value: |

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.

format: full_html processed: |

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.

summary: null field_daily_email_cta: { }