remove editors notes, acknowledge Antony

This commit is contained in:
Firehose Bot 2026-04-10 07:57:00 +02:00
parent 58ef5b73f1
commit 21acb8ebe6

View File

@ -106,7 +106,6 @@ Versioning is built in. Every export is numbered. If a BU enriches a case after
## Why a POC got this far, this fast ## Why a POC got this far, this fast
*Editors note:* I told the agent to write for a more general audience. See the imaginary CFO below. This section does get a bit technical. See it as an FYI, but I am confident some of my more technical readers will appreciate it.
Three things made the build feel unreasonably quick: Three things made the build feel unreasonably quick:
@ -117,7 +116,6 @@ Three things made the build feel unreasonably quick:
The hard problem was never the code. It was agreeing *what* to build. Once the spec was right, the build was a formality. The hard problem was never the code. It was agreeing *what* to build. Once the spec was right, the build was a formality.
*Editors note:* I did find some defects preparing the blog posts. 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.
## What a CFO should take away ## What a CFO should take away
@ -126,9 +124,12 @@ The hard problem was never the code. It was agreeing *what* to build. Once the s
- **Opt-in tiers avoid the big-bang trap.** The reason central systems fail isn't usually technical — it's that rollout requires unanimous agreement. Three tiers let each BU join on their own terms. Value compounds as more BUs join, but no single BU is blocking the others. - **Opt-in tiers avoid the big-bang trap.** The reason central systems fail isn't usually technical — it's that rollout requires unanimous agreement. Three tiers let each BU join on their own terms. Value compounds as more BUs join, but no single BU is blocking the others.
- **Spec-first design pays back quickly.** A week of elicitation saved weeks of rework. In a world where the LLMs can write most of the code, the bottleneck moves to understanding what you want. - **Spec-first design pays back quickly.** A week of elicitation saved weeks of rework. In a world where the LLMs can write most of the code, the bottleneck moves to understanding what you want.
*Editors note:* 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.
If you're at a large organisation and you're still trying to solve a cross-BU knowledge problem by building a single centralised CRM, this is the shape I'd argue you should be looking at instead. It's not a data lake. It's not a warehouse. It's a federation of small, opinionated tools that share one narrow contract, with DLP baked into the contract itself. If you're at a large organisation and you're still trying to solve a cross-BU knowledge problem by building a single centralised CRM, this is the shape I'd argue you should be looking at instead. It's not a data lake. It's not a warehouse. It's a federation of small, opinionated tools that share one narrow contract, with DLP baked into the contract itself.
The POC exists. The redaction works. The tests pass. It would ship. The POC exists. The redaction works. The tests pass. It would ship.
# Acknowledgements
(written by hand)
Thanks to [Antony Marcano](https://antonymarcano.com/) for feedback on the first version. :w