From dbe1323c0b0e38e3184907cf88d1275f0eae0758 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Sat, 28 Dec 2024 14:17:52 +0000 Subject: [PATCH] Add daily email for 2024-12-26 The more differences there are, the more likely there will be bugs --- source/_daily_emails/2024-12-26.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 source/_daily_emails/2024-12-26.md diff --git a/source/_daily_emails/2024-12-26.md b/source/_daily_emails/2024-12-26.md new file mode 100644 index 00000000..7092becc --- /dev/null +++ b/source/_daily_emails/2024-12-26.md @@ -0,0 +1,30 @@ +--- +title: The more differences there are, the more likely there will be bugs +date: 2024-12-26 +permalink: daily/2024/12/26/differences +tags: + - software-development + # - drupal + # - drupal-planet + # - php + # - podcast +cta: ~ +snippet: | + The more differences there are between your environments, the more likely there will be issues or bugs. +--- + +The [harder it is to update an environment][0], the less often it will be done and the more out of sync your environments will become. + +The more out of sync your environments are, the higher the chance there will be bugs or issues when changes are moved between environments. + +I've had situations where the code I wrote worked for my local database but didn't when moved to staging or production. + +I worked at one company where my development database was refreshed nightly, so my site was at most one day out of sync with production. + +I knew my code would work with the latest production data and not only the data from days, weeks or months before. + +It also meant that I needed to write my changes in an automated and repeatable way so they would be executed on the refreshed database and re-added instead of having to do it manually. + +How in sync are your environments and how similar to production is the environment you're testing against? + +[0]: {{site.url}}/daily/2024/12/24/moving-changes