mostalive/firehose
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add afterword

Browse Source
This commit is contained in:
Firehose Bot 2026-04-10 08:10:22 +02:00
parent 21acb8ebe6
commit 03a653cc86
1 changed files with 18 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
app/priv/blog/engineering/2026/04-09-a-thin-slice-for-federated-collaboration.md
View File

@ -8,7 +8,7 @@
---
# Prototyping fairly deep and fast
This text from "The problem" section onwards was lightly edited by me, the first pass was generated by a coding agent, based on the session the prototype was developed in. It is not the tone I would write in, but there is something to it.
This text from "The problem" section onwards was lightly edited by me, the first pass was generated by a coding agent, based on the session the prototype was developed in. It is not the tone I would write in, but there is something to it. I've written more commentary on the writing and development process in the _Afterword_.
*Prototyping is like a mirror - what is wanted (and what not) is clearer after it has been built. Building quality in, even for a prototype, can let the exploration go deeper, in more detail without spiraling out of control.*
@ -129,7 +129,23 @@ If you're at a large organisation and you're still trying to solve a cross-BU kn
The POC exists. The redaction works. The tests pass. It would ship.
# Acknowledgements
# Afterword
(written by hand)
I created this and the follow on blog post with a single prompt (for a plan) and some iteration on what the audience should be etc.
I told the agent to write for a more general audience. The "What a CFO should take away" section is a good example of that. "Why a PO got this far, this fast" does get a bit more technical than I expected. See it as an FYI, but I am confident some of my more technical readers will appreciate it.
I did find some defects in the software preparing the blog posts. One of the screenshots in the auto-generated demo contained a clear error. Working in somewhat smaller steps could have prevented this.
I wanted to see where the solution went, quickly. For production work I check the tests and code against the spec, update any of them as needed, and look more closely at what was produced, including e.g. exploratory testing and user feedback.
The agent mentions "Spec-first development". There was a formal specification involved, not just text. The process was more an iterative conversation than writing the spec out in full before starting. But this was hours, not weeks as it was just me and the animatronic rubber duck in the chat. Making tacit knowledge explicit takes people and time. Working software can help to flush that out, combined with workshops. More about the formal specification in the next post.
# Acknowledgements
Thanks to [Antony Marcano](https://antonymarcano.com/) for feedback on the first version. :w