diff --git a/src/content/daily-email/2023-08-21.md b/src/content/daily-email/2023-08-21.md
new file mode 100644
index 000000000..d1cf6ea57
--- /dev/null
+++ b/src/content/daily-email/2023-08-21.md
@@ -0,0 +1,27 @@
+---
+title: >
+  Which part of the CI pipeline has the most value?
+pubDate: 2023-08-21
+permalink: >
+  archive/2023/08/21/which-part-of-the-ci-pipeline-has-the-most-value
+tags:
+  - continuous-integration
+  - automated-testing
+  - static-analysis
+---
+
+The main part of my CI pipeline tasks are running the automated tests, coding standards checks and static analysis.
+
+But which of these are the most valuable?
+
+I used to run the coding standards check first as it was the quickest, followed by static analysis and the automated tests.
+
+If a task were going to fail, it would fail quickly.
+
+But is that the objective of the CI pipeline?
+
+Whilst it needs to be quick, the main reason to run these is to ensure things work as expected.
+
+Recently, I changed my pipelines to run the tests first, as these verify the code's behaviour.
+
+I want to know if the code works but has a coding standard error that needs to be fixed rather than the pipeline failing on the error and not knowing whether the code works.