publish, and fix description

.gitignore

@@ -25,3 +25,4 @@ Screenshot*.png
 
 # nono sandbox scratch space
 nono/
+/.DS_Store

app/priv/blog/engineering/2026/03-16-hello-world.md

@@ -1,9 +0,0 @@
-%{
-  title: "Hello World",
-  author: "Firehose Team",
-  published: false,
-  tags: ~w(elixir phoenix),
-  description: "Our first engineering blog post"
-}
----
-Welcome to the Firehose engineering blog! We'll be sharing deep dives into our tech stack here.

app/priv/blog/engineering/2026/10-29-the-intention-location-details-communication-pattern.md

@@ -0,0 +1,39 @@
+%{
+  title: "The Intention, Location, Details communication Pattern",
+  author: "Willem van den Ende",
+  tags: ~w(),
+  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: 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.
+
+I find this pattern “Intention, Location Details” by [Emily Bache](https://coding-is-like-cooking.info) quite handy, and it is food for thought for AI augmented work. It took me a while to find sources, so I am collecting them here, before expanding on my own musings.
+
+I came across this pattern, as I was going through  [Emily Bache](https://coding-is-like-cooking.info) ’s post [Agentic AI coding breaks Mob programming](https://coding-is-like-cooking.info/2026/10/agentic-ai-coding-breaks-mob-programming-heres-how-to-fix-it/)  . In it, there is a paragraph on the Intention, Location, Details communication pattern, aimed at working together effectively in an ensemble:
+
+> To keep everyone aligned and to enable smooth transition between roles, I also teach the communication pattern ‘Intention, location, details’.
+> 
+> This means the talker keeps everyone on board by frequently explaining their ‘intention’. Sometimes they need to go to ‘location’ – point at somewhere on the screen or in the codebase, and once everyone’s attention is on that, it’s clear what they mean. Occasionally that’s not enough and they give explicit ‘detail’ so the ‘typist’ gets told exactly what to do.
+> 
+> In the main though, you communicate intention, so when you rotate roles, the next person should have a good idea about where the previous person was headed, and can seamlessly take over. 
+
+## More sources
+
+[Emily Bache](https://coding-is-like-cooking.info) says she learnt this pattern from [Llewellyn Falco](https://llewellynfalco.blogspot.com/). Emily’s  [Samman coaching book](https://emilybache.com/samman-coaching-book/)[https://sammancoaching.org](https://sammancoaching.org) has it on page 27. I have read the book, and would recommend, but didn’t notice it as I went through it.
+
+I found that the pattern was in the book through [Jo van Eyck](https://jovaneyck.github.io/)’s video [IMMEDIATELY improve your pair programming skills with “intention, location, detail”](https://www.youtube.com/watch?v=kG70AzY44GY) .
+
+Jo’s video description refers to a learning hour that is now a dead link. I guess it is now the [Talking with Intent, Typing Syntax](https://sammancoaching.org/learning_hours/ensemble/talking_typing.html) learning our, which also contains a description of the pattern.
+
+## More rambling
+
+Now that I have finally put the words in a comprehensible order, the pattern is not in a recognisable pattern form. But it does fit many contexts. Intent(ion), location and details in a sense are each micro patterns. Provide clear intent. When the intent is not clear enough, clarify, or point at the location (this is the context for Location). When location (more context) is not enough, provide details.
+
+I associate this with [Commanders Intent](https://www.mca-marines.org/gazette/commanders-intent-easy-to-understand-tough-to-articulate/) and  Backbriefing, as explained in the book [The Art of Action](https://www.stephenbungay.com/Books.ink). What I like about the pattern description above, is that fits in a paragraph, is that the explanation does not require any background. It took a while before I made it through  [The Art of Action](https://www.stephenbungay.com/Books.ink), and the lessons from it gelling appears to be a process that is taking me years.
+
+How about you? Do you often provide details where clear intent might have worked better? (micro management) Does intent sometimes surface **after** providing location and details? (hindsight from working through it) I am curious. The devil is, as always, is in the intent(ion).
+
+Happy communicating, read you next time!