From 8fa342e80d22a0b92bf009bdea6a96878d55ad1a Mon Sep 17 00:00:00 2001 From: Firehose Bot Date: Thu, 29 Oct 2026 17:00:29 +0000 Subject: [PATCH] publish, and fix description --- ...9-the-intention-location-details-communication-pattern.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/app/priv/blog/engineering/2026/10-29-the-intention-location-details-communication-pattern.md b/app/priv/blog/engineering/2026/10-29-the-intention-location-details-communication-pattern.md index 41fbe4e..60c25fc 100644 --- a/app/priv/blog/engineering/2026/10-29-the-intention-location-details-communication-pattern.md +++ b/app/priv/blog/engineering/2026/10-29-the-intention-location-details-communication-pattern.md @@ -2,9 +2,10 @@ title: "The Intention, Location, Details communication Pattern", author: "Willem van den Ende", tags: ~w(), - description: "When developing software, helping others do it, or instructing language models, it helps when we are clear about why we want to change something, where the change should happen(or not) and…", + description: "Communicating our intent clearly is helpful in getting the results we want. I find the pattern “Intention, Location Details” as described by Emily Bache quite handy, It took me a while to find sources, I am collecting them here, before expanding on my own musings." +", image: nil, - published: false + published: true } --- When developing software, helping others do it, or instructing language models, it helps when we are clear about why we want to change something, [where the change should happen](https://www.qwan.eu/2020/12/23/what-to-put-where.html) (or not) and occasionally be very precise in what the change should be.