Anthropic just released Claude Fable 5 — the public version of the Mythos-class model that found thousands of zero-days and escaped its own sandbox in testing. Why Spec-Driven Development is now non-negotiable: open.substack.com/pub/kentka… #AI #SpecDrivenDevelopment #AISafety

Anthropic just released Claude Fable 5 — the public version of the Mythos-class model that found thousands of zero-days and escaped its own sandbox in testing. Why Spec-Driven Development is now non-negotiable: open.substack.com/pub/kentka… #AI #SpecDrivenDevelopment #AISafety

Daily Tech Digest - June 12, 2026 highlights how context compression is finally working in production, reshaping how AI systems retain and reason over long‑horizon information. #AIAgents #AIRegulation #AlertFatigue #ContextEngineering #DataQuality #DigitalWorkforce #InferencingCost #QuantumComputing #SolutionArchitecture #SpecDrivenDevelopment links.kannan-subbiah.com/202…

Most AI coding tools let you type a prompt, hope for the best, and deal with the consequences later. Kiro takes a different approach: you write the spec first, and the AI actually has something useful to work from. Not a vague instruction you typed in 30 seconds. A real description of what the feature should do, how it should behave, and what counts as broken. Turns out that matters quite a bit when you're the one reviewing the output at 11pm. Ata Ağrı (AI Champion at kloia) is going live on June 10th to walk through spec-driven development with Kiro from start to finish. 45 minutes. Free. Online. No slides that could've been an email. 👉 Register: meetup.com/kloia-meetup-grou… #Kiro #SpecDrivenDevelopment #SoftwareEngineering #AICode

"Just do it" should be the motto of AI-driven development. Too many people build theories and polish concepts that never touch a real project. With AI moving this fast, those concepts are outdated before they ever ship. But raw "just do it" is also a trap. If you only act and never reflect, you build the same broken workflow ten times without noticing. The real shift is speed and grounding. Do not spend six months on a concept and then test it. Build it, see what breaks, adjust. Theory should come from practice, not before it. One thing that helps: know your half-lives. Tool level knowledge (which prompt, which model, which CLI flag) is dead in weeks. The principles you abstract from real work last much longer. Keep the spec tight. Take brownfield context seriously. Always review the output. Do not confuse the two, or you will be holding something dead in six months. Think less at the whiteboard. Think closer to the code. #AIUP #SpecDrivenDevelopment

Spec-driven Development ist für mich der Weg, wie KI-gestützte Entwicklung im Enterprise-Umfeld wirklich funktioniert. An den Workshop-Tagen 2026 zeige ich, wie das geht. In meinem ganztägigen Workshop "Spec-driven Development mit dem AI Unified Process" führe ich dich durch den gesamten Prozess: von der Vision über den Anforderungskatalog bis zur lauffähigen Software. Wir arbeiten mit Claude Code, Skills und MCP für Vaadin, jOOQ, Karibu Testing und Playwright. 📅 8. September 2026, ganztägig 📍 Raum F91 Wenn du verstehen willst, wie klare Spezifikationen und KI zusammenspielen, bist du hier richtig. #AIUP #SpecDrivenDevelopment #Java #Vaadin #SpringBoot #jOOQ

Building MCP Eavesdrop Part 2: levelup.gitconnected.com/bui… #ai #mcp #specdrivendevelopment #agentic #vscode #cursor #observability

Building MCP Eavesdrop Part 1: levelup.gitconnected.com/bui… #ai #mcp #specdrivendevelopment #agentic #vscode #cursor #observability

I had a great time at Spring Office Hours! We talked about Spec-Driven Development. Thank you @therealdanvega for having me! Watch the short clip here: youtube.com/shorts/ns8C_F6dF… And the full session is here: youtube.com/live/BZjQo0OJD_A #SpringBoot #SpecDrivenDevelopment #springofficehours

Ahora tengo SPEC.MD, PLAN.MD y TASKS.MD por cada de las feature. 24 minutos invertidos. Pero te aseguro que el resultado, será el esperado y no el que el LLM creé. #SDD #AI #SpecDrivenDevelopment

I’m working within huge investment bank. There was lots of actions toward AI first initiatives. Forced track of “spent token” if you not spending much - you lacking of skill, that how management start to evaluate performance. After 2y of constant #specdrivendevelopment #ai they silently cut limits. Now all tokens within corporate copilot is x25. Basically you out of monthly tokens allowance after 5-6 well put promts. What would be the next steps?

The recording of my second GIDS 2026 talk is now online. "Spec-Driven Development: How AI Changes Everything (And Nothing)" This is a new way to build software. You write your requirements once. Then AI generates the rest: diagrams, models, and code. When the requirements change, everything updates with them. No more outdated docs. In this talk I start from a real system use case and build a full-stack Java application live with AI. You will see how to write requirements that AI understands, and how to keep everything connected from the business need down to working code. This is not about replacing developers. It is about letting AI handle the boring parts, so we can focus on what really matters: understanding what the business needs. Watch it here: youtu.be/82lCQdG6CsU #Java #SpringBoot #Vaadin #jOOQ #AI #SpecDrivenDevelopment #GIDS2026

We learned to shift testing left. Then security. Now it is the spec's turn. Here is the problem. For years, specs had a strange place in our work. We wrote a few pages at the start, and then the real specification happened inside the code. Developers filled the gaps with judgement. The document and the running system slowly drifted apart. That worked because a human read the thin spec and asked the right questions. AI changes the economics. Code is cheap to produce now. So the value moves. It is no longer in typing the code. It is in knowing what to build. And here is the risk: a vague spec used to give you slow, messy code. Now it gives you fast, messy code. Garbage in, garbage out, only faster. This is the core idea in the AI Unified Process (AIUP). We move the spec to the left and make it the first artifact, not a by-product. We review the spec, not only the code. The thinking happens up front, where it is cheap. And the spec stays the single source of truth that drives the generation. It is not waterfall. We still work in small increments. Inside each one, the spec comes first, then the code. Specify a little, generate, learn, refine. Code is cheap now. Clarity is the scarce thing. New blog post: martinelli.ch/shift-left-get… #AIUP #SpecDrivenDevelopment #SoftwareEngineering #AI

“AI is making specifications a first-class engineering artefact again.” For years, we treated specs as paperwork. Now they're becoming one of the most valuable assets in software engineering. Because AI can generate the code. But it still needs: ✅ clear intent ✅ clear context ✅ clear requirements The teams that win with AI won't be the ones writing the most code. They'll be the ones writing the best specifications. New Serverless CrAIc episode 👇 theserverlessedge.com/spec-d… #AI #SoftwareEngineering #SpecDrivenDevelopment #AIEngineering

The IT industry loves tools. Every problem becomes a tool problem. And with AI, this has become even stronger. Every week, hundreds of new tools appear. New plugins, new skill collections, new workflow engines, new platforms. But maybe we should stop for a moment. What problem are we actually trying to solve? In many cases, the answer is not: we need another tool. The answer is: we need a better process. That is why I created the AI Unified Process. Not as another tool, but as a way to structure the work before the tools start working. unifiedprocess.ai Because the real bottleneck is not code generation. The real bottleneck is clarity. Clear requirements. Clear use cases. Clear domain concepts. Clear decisions. Once that is in place, tools can help a lot. Without it, they only help us create confusion faster. Maybe it is time for a small counter-movement. The No Tools Movement. Less tool chasing. More thinking. #AIUnifiedProcess #SpecDrivenDevelopment #SoftwareEngineering #AI #NoToolsMovement

What a blast! 🚀 Yesterday I had the pleasure of speaking at the @vaadin webinar about Spec-Driven Development with AI. We talked about how AI coding tools can generate code fast, but without clear requirements and review points, they often speed up the old problems too: outdated docs, unclear intent, and code as the only source of truth. In the session, I showed a practical workflow where requirements stay in the center, and AI helps to generate and maintain use cases, diagrams, specs, code, and tests. The goal is better traceability, business alignment, and maintainability. A big thank you to Mikka for hosting the session and running the Q&A so well, and to the whole Vaadin team for having me. It was a lot of fun! Did you miss it? You can watch the recording here: youtube.com/live/IFds3VDRVCw #Vaadin #SpecDrivenDevelopment #AIUP #Java #SpringBoot #jOOQ

In my AI Unified Process talks, I can now show something live that I could not show before. I can recreate the whole Spring PetClinic on the "Simon Martinelli stack": Vaadin, Spring Boot, and jOOQ. The interesting part is the order of work. First, I reverse engineer the use cases and the entity model. That is the spec. This is done as a separate step. Then Claude Code with Opus 4.8 takes that spec and builds the app, including browserless tests with Vaadin's new open source Browserless Testing. Time for that part: 18 minutes and 27 seconds. So the slow work goes into the spec. Once the spec is good, the implementation and the tests are fast and repeatable. That is the core idea of AIUP: requirements first, then let the agent build. PetClinic is perfect for this because everyone knows it. People can see what the reverse engineering produced and judge the result themselves. #AIUP #Java #SpringBoot #Vaadin #jOOQ #SpecDrivenDevelopment #ClaudeCode

Te venden como “nueva metodología para programar con IA” algo que tiene más de 60 años. Le cambian el nombre, le meten AI, agentic y vibe coding… pero la idea es la de siempre: primero piensas. luego construyes. La IA programa. No lee tu cabeza. #SDD #SpecDrivenDevelopment

The recording of my talk at AI fokus is now online! 🎥 In this session, I shared how Spec-Driven Development changes the way we build software with AI. Instead of putting code in the center, we make requirements the source of truth and let AI help us stay consistent across specs, models, and implementation. A big thank you to the organizers of AI fokus for putting together such a great event and for inviting me to speak. The energy in the room and the conversations afterwards were fantastic. If you want to see how AIUP (AI Unified Process) brings structure to AI-assisted development, here is the recording: 👉 youtube.com/watch?v=kQj-_2Jd… I would love to hear your thoughts. How are you using AI in your development process today? #AIUP #SpecDrivenDevelopment #SoftwareEngineering #AI #Java