<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Waterfall on Gniewomir Świechowski</title>
    <link>https://gniewomir.com/tags/waterfall/</link>
    <description>Recent content in Waterfall on Gniewomir Świechowski</description>
    <image>
      <title>Gniewomir Świechowski</title>
      <url>https://gniewomir.com/images/papermod-cover.png</url>
      <link>https://gniewomir.com/images/papermod-cover.png</link>
    </image>
    <generator>Hugo -- 0.147.8</generator>
    <language>en</language>
    <lastBuildDate>Wed, 12 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://gniewomir.com/tags/waterfall/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Waterfall-in-disguise&#39;s return is just around the corner</title>
      <link>https://gniewomir.com/posts/waterfall-in-disguises-return-is-just-around-the-corner/</link>
      <pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://gniewomir.com/posts/waterfall-in-disguises-return-is-just-around-the-corner/</guid>
      <description>&lt;p&gt;Waterfall-in-disguise&amp;rsquo;s return is just around the corner. If we allow it, we will be even more miserable than we already are with &amp;ldquo;scrum&amp;rdquo; cargo-cult.&lt;/p&gt;
&lt;p&gt;For the second time in the last year I will be writing minimal OAuth2 auth server (why that is material for another note). Creating &amp;amp; refining initial spec took a full day of work so far - before even one LOC was created.&lt;/p&gt;
&lt;p&gt;The model&amp;rsquo;s ability to spot underspecified requirements or contradictions with chosen RFC baseline is a godsend when working with a sensitive domain like security. Makes good spec cheap, not resurrecting waterfall by itself. Still, three serious problems follow:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
