Mastodawn

"Our thesis is that code should not be maintained - code should be regenerated. Specs should be reviewed, and it’s the specs that you maintain.” by Paul Sawers

https://thenewstack.io/codeplain-spec-driven-regenerative-code/

#artificialintelligence #specDrivenDevelopment

"Code should be regenerated, not maintained": Codeplain makes the case for spec-driven development

The phoenix of Greek myth burns and is reborn from its own ashes -- a metaphor this founder is applying to AI-generated code.

The New Stack

robrich 5d ago

https://www.linkedin.com/posts/dmitry-demidenko_spec-driven-development-is-having-a-moment-share-7463015640250044416-_0qh/ - Is #SpecDrivenDevelopment a new thing? Or just "clear and unambiguous #requirements", an idea from Dan North in 2006? Great point https://www.linkedin.com/in/dmitry-demidenko.

Spec-Driven Development is having a moment. GitHub shipped spec-kit. OpenAI is pushing "natural language as the new programming language." Every AI tooling pitch is a variation of: write the spec… | Dmitry Demidenko | 25 comments

Spec-Driven Development is having a moment. GitHub shipped spec-kit. OpenAI is pushing "natural language as the new programming language." Every AI tooling pitch is a variation of: write the spec, hand it to the model, get the code. The framing is misleading. Dave Farley has been telling you to do this for fifteen years. Dan North coined BDD in 2006. The point was always the same: write requirements in a form that is unambiguous and executable. Code is a byproduct of clearly stating what you want. Most teams ignored it. Gherkin became ceremony. Cucumber became a graveyard. The discipline was right; the payoff was diffuse. What changed isn't the philosophy. It's the economics. BDD asked engineers to do extra work for a payoff they couldn't feel. LLMs punish vague specs in real time — hand a model an ambiguous spec, it confidently ships the wrong thing in twenty seconds. The feedback loop BDD always wanted finally exists, because imprecision now costs you visibly and immediately. The rigor was always the point. AI just made the rigor pay. Practical implication for founders hiring engineers: the people who can actually do SDD well are the people who could have done BDD well. They think in invariants. They write specs that exclude ambiguity. Give them Claude or Codex and they ship like a team of four. Give the prompt-and-pray crowd the same tools and they ship technical debt at four times the rate. Skip "have you used Cursor" in your next interview. Ask them to walk through how they would specify a non-trivial feature before writing any code. The answer tells you everything. | 25 comments on LinkedIn

Mathew Attlee Jun 8

This is a fascinating read about the history of Waterfall, Agile and whether spec-driven development is Waterfall or something else. https://blog.herlein.com/post/is-waterfall-back/ #SpecDrivenDevelopment

Is Waterfall Coming Back? Sort Of. Not Really. Both — And the Bigger Question Underneath. · Greg Herlein

industrial curiosity Jun 8

Building MCP Eavesdrop Part 2: https://levelup.gitconnected.com/building-mcp-eavesdrop-part-2-638e54c8651e?source=social.tw

#ai #mcp #specdrivendevelopment #agentic #vscode #cursor #observability

Building MCP Eavesdrop Part 2:

Building and publishing your VSCode extension

Medium

industrial curiosity Jun 8

Building MCP Eavesdrop Part 1: https://levelup.gitconnected.com/building-mcp-eavesdrop-part-1-d90937072659?source=social.tw

#ai #mcp #specdrivendevelopment #agentic #vscode #cursor #observability

Building MCP Eavesdrop Part 1:

Building a VSCode extension with AI and OpenSpec

Medium

Jeferson 'Shin'Jun 4

What are these people seeing that I'm not, what is this level of crazy performance hits that they are talking that I'm not seeing?

https://jeferson.me/blog/2026/06/04/what-are-they-seeing

#AI #Architecture #Artificial #Bubble #Coding #Development #Documentation #Eliza #Game #GameDev #Intelligence #Layoffs #MachineLearning #OpenSource #Productivity #Refactoring #Rsync #Slop #Software #SpecDrivenDevelopment #Turing #VibeCoding #Waterfall

What are they seeing?

What are these people seeing that I'm not. Am I this level of stupid? Or should I start to embrace the dumb?

InfoQ May 20

#SoftwareSpecifications can now serve as a dynamic source of truth, as LLM-based reasoning agents become better at interpreting human ambiguity.

The catch? #LLMs are stochastic and must be constrained.

Enter #ContextEngineering - a structured discipline focused on providing clear intent and missing instructions to AI models.

It relies heavily on context artifacts, including: ⇨ Skills ⇨ Rules ⇨ Scripts ⇨ Feedback loops ⇨ Evaluation metrics

🎧 Hear more insights on the #InfoQ #podcast with Baruch Sadogursky: https://bit.ly/49dArFj

📄 #transcript included

#SoftwareArchitecture #SpecDrivenDevelopment #Testing #AI #SoftwareEngineering

Sheena May 20

On 3 June I'll be presenting at #PyData Johannesburg, South Africa.
I'll be sharing some details of my own #SpecDrivenDevelopment #Agentic #SoftwareEngineering workflow.
RSVP here: https://www.meetup.com/pydata-johannesburg/events/314582868

Also, I have a few #ClaudeMax vouchers to give away while I'm there (Thanks #Anthropic )

Generating Code Faster Than You Can Debug It, Wed, Jun 3, 2026, 6:30 PM | Meetup

**Generating code faster than you can debug it?** You’re not the only one. Velocity is up. Clarity hasn’t caught up. PyData is where we compare what actually holds up in pr

Meetup