The Farmer Kept the Farm

The country turned 250 last weekend. The fighting had started fifteen months before there was a country to fight for.

On the morning of April 19, 1775, about seventy men stood on Lexington Green. Most had been working their fields the day before. A few had fought the French and Indians twenty years earlier. They drilled on that common most weeks, then walked home and finished the chores.

We tell this story wrong. The popular version has untrained farmers humbling a professional army, and that is not what happened. Three winters later Washington was at Valley Forge handing his army to a Prussian named von Steuben, who wrote a drill manual, because a collection of local militias could not beat a standing army.

The Minuteman’s value sat somewhere else. He was a farmer who could also fight, and he never stopped being a farmer. He brought ground he already knew.

One of our lead architects has spent his career producing diagrams and design documents. Models, specifications, the drawings that sit way upstream of anything anyone ships. He is not an engineer. His entire output was paper. Very important paper.

Then he built an agentic workflow on our citizen developer platform. Hand it a requirement and it reasons out which systems it touches, which teams it affects, and where it lands in the customer’s journey. It writes the work back into our task system. It populates a graph database that gets sharper every time somebody uses it.

He is still an architect. Same documents, same reviews, same judgment about what belongs in them. What changed is that he built the machine that produces them.

AI hands anyone roughly eighty percent of the engineering. The twenty percent that closes it is knowing which systems matter and what a design document has to say, and that is what he spent a career acquiring.

The best slide in his overview presentation lists what the thing is not. Human architects and platform engineers stay in the decision loop. Treat it as a proof of value rather than a finished product. He built something impressive and then wrote down its limits, which is the part almost nobody does. It is on track to serve hundreds of people and take weeks out of the march from requirement to production.

Steuben’s contribution to the war was a manual. He wrote down how it is done and where the edges are.

The militia showed up on the first morning. The Prussian wrote the book. This architect did both.

The fighting started before there was a country. The building starts before the org chart has a word for it.

Whatever your practice is, an engineering version of it exists now.

Go be that.