# Scott Werner - Warranty Void if Regenerated (Highlights)  ## Metadata **Review**:: [readwise.io](https://readwise.io/bookreview/59126865) **Source**:: #from/readwise #from/reader **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Scott Werner]] **Full Title**:: Warranty Void if Regenerated **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **Document Tags**:: #favorite **URL**:: [nearzero.software](https://nearzero.software/p/warranty-void-if-regenerated) **Host**:: [[nearzero.software]] **Highlighted**:: [[2026-03-19]] **Created**:: [[2026-03-21]] ## Highlights - People who understood the domain and could also diagnose specification problems were the most valuable people in any industry ([View Highlight](https://read.readwise.io/read/01km2ybcqkzb8j9xz37c3ec8hn)) ^998404191 - The spec described a static relationship between inputs and outputs, but the inputs were alive (feeds from other systems that were themselves being updated, recalibrated, and regenerated constantly). ([View Highlight](https://read.readwise.io/read/01km2znhk62tkgbz2v6n4a20r9)) ^998406704 - The idea that software needed continuous tending because the world around it moved was counterintuitive to people whose other tools stayed reliably what they were. ([View Highlight](https://read.readwise.io/read/01km2zvhegk153z2c0qpssek86)) ^998407111 - Tom had concluded that this was not a problem of economics but of psychology: paying for maintenance meant admitting vulnerability, while paying for repair meant responding to an emergency, and humans found emergencies much more motivating than vulnerabilities. ([View Highlight](https://read.readwise.io/read/01km2zyphy02h14dhsbrmg0ns2)) ^998407237 - A Software Choreographer would map your entire tool ecosystem, specify the interfaces between them, build a conformance layer so that when any tool regenerates, the interfaces are verified before the new version goes live. ([View Highlight](https://read.readwise.io/read/01km306e32rbkmrk8badre1aej)) ^998407483 - Shipping containers were cheap. Organizing container logistics (the ports, the cranes, the rail connections, the tracking systems, the customs protocols) was where all the value and all the jobs were. The container was the easy part. The system was the hard part. ([View Highlight](https://read.readwise.io/read/01km307y6gb4y4f6m6gp2a3taj)) ^998407587 - What they couldn’t do was encode the kind of knowledge that accumulates over decades of physical presence in a specific place — the clay underneath the greenhouse, the deer path that compacted the soil in the northeast corner, the way the prevailing west wind dried the far rows faster than the ones sheltered by the tree line. This knowledge was in Carol’s head, not in any database, and it was precisely the kind of knowledge that natural-language specifications were worst at capturing, because it was embodied, contextual, and often inarticulable. ([View Highlight](https://read.readwise.io/read/01km30p97479x2b645pbthgr99)) ^998408241 - The third option was the one Tom suspected she’d choose: use the system as a baseline and let Carol override it. The system would run Tyler’s optimization, but Carol would have a physical override switch (a real switch, mounted on the wall, that she could flip to take manual control whenever she wanted). The system would log when she overrode it and why, and over time, those overrides would become data that could be fed back into the spec, gradually incorporating her knowledge. ([View Highlight](https://read.readwise.io/read/01km30s0ajwxc2qvn5bzetjqjc)) ^998408443 - Tom had learned early in his career to always offer a physical control. A button. A switch. A lever. Something the client could touch. ([View Highlight](https://read.readwise.io/read/01km30t8k26abyr86ve17wwkew)) ^998408542