From 693b74f4a49ed1cba51d70fa63fcff111e4e466d Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Thu, 15 Jun 2023 00:31:27 +0100 Subject: [PATCH] daily-email: add 2023-06-11 Failing fast --- src/content/daily-email/2023-06-11.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 src/content/daily-email/2023-06-11.md diff --git a/src/content/daily-email/2023-06-11.md b/src/content/daily-email/2023-06-11.md new file mode 100644 index 00000000..8cac2921 --- /dev/null +++ b/src/content/daily-email/2023-06-11.md @@ -0,0 +1,14 @@ +--- +title: > + Failing fast +pubDate: 2023-06-11 +permalink: > + archive/2023/06/11/failing-fast +tags: [] +--- + +Usually, failing fast in software development refers to errors in code, but another interpretation of this is "What's the quickest and simplest way to validate or prove an idea"? + +If it's fixing a bug or architecting a new feature, what's the simplest thing that can be done to achieve that? It could be writing a technical document or creating a simple proof of concept rather than building the entire feature. + +If it fails, your sunk cost is low as you've not invested much time, money or energy.