From 891e7003ff9c279625da76e1275e2d560aa9e0d9 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Sat, 9 Mar 2024 21:06:49 +0000 Subject: [PATCH] Add daily email for 2024-03-07 Why write software for this? --- source/_daily_emails/2024-03-07.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 source/_daily_emails/2024-03-07.md diff --git a/source/_daily_emails/2024-03-07.md b/source/_daily_emails/2024-03-07.md new file mode 100644 index 000000000..6618cd463 --- /dev/null +++ b/source/_daily_emails/2024-03-07.md @@ -0,0 +1,28 @@ +--- +title: Why write software for this? +date: 2024-03-07 +permalink: archive/2024/03/07/why-write-software-for-this +tags: + - software-development +cta: ~ +snippet: | + What questions do you ask when speaking to prospective clients? +--- + +Recently, when speaking with prospective clients, instead of focusing on the features they want, I like to ask questions like: + +What's wrong with what you have now? + +Why not fix what you have instead of rebuilding? + +What problem are you trying to solve? + +Why write software for this at all? + +Why not do it manually? + +Why do you need to do this now? + +What results would you expect to see after this project? + +If they can answer these types of questions and explain the business outcomes they're looking to achieve and what value I can add, those are the projects I want to work on.