Taste Is in the Spec (Cooking Is Not the Recipe) (blog.herlein.com)
from codeinabox@programming.dev to programming@programming.dev on 28 Jun 11:30
https://programming.dev/post/52690429

#programming

threaded - newest

hdsrob@lemmy.world on 28 Jun 11:39 collapse

Another article trying to solve the problems of using AI in development with better specs or better prompts instead of just writing the fucking code.

codeinabox@programming.dev on 28 Jun 12:14 collapse

This article is not advocating AI driven development. It’s arguing a human understanding the problem, and how best to solve it, is the most important work.

I’m not anti-spec. Far from it. I think rigorous, well-structured specs are about to be the single most important artifact in software. Read the book. Adopt the format. Use the tools. The mechanics matter and I’m not waving them away.

But the spec is a vessel. The recipe is not the cooking. If we pour mediocre understanding into a perfectly-formatted spec, we get perfectly-formatted slop, faster and at scale. The format is necessary. It is nowhere near sufficient.

The real work - the part no tool will do for you - is the human work of digging in. Of actually understanding the problem and the person you’re solving it for, deeply enough to have an opinion about what right feels like. Of capturing not just the requirements but the taste. The why. The elegance. The exact sweet spot of how it should work.

Feyd@programming.dev on 28 Jun 13:15 collapse

Followed by:

I’ve been deep in the new spec-driven literature. There’s a book - Agentic Spec-Driven Development: A Practical Method for Using AI to Build Complete Specifications