11 hours ago · 6 min read1205 words · Tech · hide · 0 comments

I’ve been having this almost-debate with Matt Pocock for a while about the best way to do spec driven development.Matt is a very accomplished old-school developer. A true software engineer. And he’s been using AI to enhance his capabilities to an extraordinary degree. His development skills are extremely powerful, and have been starred more than almost any other skills repo on GitHub.So what’s my disagreement?Basically I think he is at the top of the mountain for the old way of doing things. He’s got tons of skills and tons of commands. And having a human in the loop is a major theme for him.But his central idea lately has been that the most important thing in a development project is the code itself. That specs are useful and everything, but the code itself is the main artifact. The source of truth for everything.I disagree strongly. I think the articulation of what you’re building, and why, is far more important. Basically, the idea. Your intent.I think the most important thing in…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.