<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Greenfield Production Systems · Writing</title><description>Essays on verification, behavior catalogs, and what it takes to trust machine-written software.</description><link>https://greenfieldproductionsystems.com/</link><language>en-us</language><item><title>From hand-fitted cars to hand-fitted code.</title><link>https://greenfieldproductionsystems.com/writing/from-hand-fitted-cars-to-hand-fitted-code/</link><guid isPermaLink="true">https://greenfieldproductionsystems.com/writing/from-hand-fitted-cars-to-hand-fitted-code/</guid><description>Around 1908, cars were built the way most software is built today: by craftsmen who held the design in their heads and made everything fit at the bench. What Ford&apos;s reorganization of work says about software in the AI age, and why the parallels run deeper than the assembly-line metaphor suggests.</description><pubDate>Wed, 08 Jul 2026 18:00:00 GMT</pubDate><author>Josh</author></item><item><title>A model can&apos;t tell you what it didn&apos;t read.</title><link>https://greenfieldproductionsystems.com/writing/a-model-cant-tell-you-what-it-didnt-read/</link><guid isPermaLink="true">https://greenfieldproductionsystems.com/writing/a-model-cant-tell-you-what-it-didnt-read/</guid><description>Point a model at a codebase nobody on the team wrote and it will summarize any file well. What it misses is the wiring between files, and a shallow reading reads identically to a correct one. The cure is not a stronger model. It is three checks that measure comprehension against the source.</description><pubDate>Wed, 17 Jun 2026 15:00:00 GMT</pubDate><author>Josh</author></item><item><title>What does production-ready mean when AI writes the code?</title><link>https://greenfieldproductionsystems.com/writing/what-does-production-ready-mean/</link><guid isPermaLink="true">https://greenfieldproductionsystems.com/writing/what-does-production-ready-mean/</guid><description>Every shop says production-ready, because the word as used costs nothing to say. Turning it into something a buyer can check takes four artifacts they can re-run without trusting you: a behavior catalog, a gate transcript, a dual-green suite, and a stated boundary.</description><pubDate>Mon, 15 Jun 2026 13:00:00 GMT</pubDate><author>Josh</author></item><item><title>What custom software should cost.</title><link>https://greenfieldproductionsystems.com/writing/what-custom-software-should-cost/</link><guid isPermaLink="true">https://greenfieldproductionsystems.com/writing/what-custom-software-should-cost/</guid><description>The number you most want before a build is the one nobody can honestly give you, because price is a function of how legible the scope is. Make the scope legible and the rest of the questions answer themselves.</description><pubDate>Mon, 15 Jun 2026 09:00:00 GMT</pubDate><author>Josh</author></item><item><title>How to choose a development partner.</title><link>https://greenfieldproductionsystems.com/writing/choosing-a-development-partner/</link><guid isPermaLink="true">https://greenfieldproductionsystems.com/writing/choosing-a-development-partner/</guid><description>Process labels and portfolios are weak predictors of how a build turns out. The variable that actually tracks outcomes is whether a team can prove its work does what it was supposed to, which is also why a redesign can quietly destroy a conversion rate.</description><pubDate>Mon, 15 Jun 2026 08:00:00 GMT</pubDate><author>Josh</author></item><item><title>Switching agencies without losing six months.</title><link>https://greenfieldproductionsystems.com/writing/switching-development-agencies/</link><guid isPermaLink="true">https://greenfieldproductionsystems.com/writing/switching-development-agencies/</guid><description>When you change development partners, the time you lose isn&apos;t the code. It&apos;s the understanding of what the code does, which lived in the old team&apos;s heads and walked out with them. An artifact fixes that.</description><pubDate>Mon, 15 Jun 2026 07:00:00 GMT</pubDate><author>Josh</author></item><item><title>Code generation was never the bottleneck.</title><link>https://greenfieldproductionsystems.com/writing/code-generation-was-never-the-bottleneck/</link><guid isPermaLink="true">https://greenfieldproductionsystems.com/writing/code-generation-was-never-the-bottleneck/</guid><description>Verification debt, the verification gap, comprehension debt: the market has named the disease from every angle. The cure is machinery that shows its work.</description><pubDate>Fri, 12 Jun 2026 09:00:00 GMT</pubDate><author>Josh</author></item><item><title>Why we retired Gherkin.</title><link>https://greenfieldproductionsystems.com/writing/why-we-retired-gherkin/</link><guid isPermaLink="true">https://greenfieldproductionsystems.com/writing/why-we-retired-gherkin/</guid><description>Our factory generated Cucumber feature files that looked exactly like what BDD promised, and the team that had to own them said no. They were right.</description><pubDate>Thu, 11 Jun 2026 09:00:00 GMT</pubDate><author>Josh</author></item></channel></rss>