<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Methodology on DevOpsTales</title>
    <link>https://devopstales.github.io/tags/methodology/</link>
    <description>Recent content in Methodology on DevOpsTales</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 17 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstales.github.io/tags/methodology/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SDD vs Vibe Coding: Waterfall with Markdown or Controlled Iteration?</title>
      <link>https://devopstales.github.io/ai/sdd-vs-vibe-coding/</link>
      <pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://devopstales.github.io/ai/sdd-vs-vibe-coding/</guid>
      <description>Spec-driven development entered 2026 as the serious developer&rsquo;s answer to vibe coding drift: implement against a reviewed specification, not an ad-hoc prompt. Hacker News called it &ldquo;Waterfall Strikes Back.&rdquo; Both sides have a point — and the practical question was never which side wins, but how much spec a specific task needs.
</description>
      <enclosure url="https://devopstales.github.io/img/sdd-vs-vibe-coding-icon.webp" length="7986" type="image/png" />
    </item>
    
  </channel>
</rss>
