<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Software on Designing Secure Software</title>
    <link>https://designingsecuresoftware.com/tags/software/</link>
    <description>Recent content in Software on Designing Secure Software</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 16 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://designingsecuresoftware.com/tags/software/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Waterfall under the bridge</title>
      <link>https://designingsecuresoftware.com/writings/waterfall/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://designingsecuresoftware.com/writings/waterfall/</guid>
      <description>&lt;h3 id=&#34;waterfall-under-the-bridge&#34;&gt;Waterfall under the bridge&lt;a class=&#34;anchor&#34; href=&#34;#waterfall-under-the-bridge&#34; aria-hidden=&#34;true&#34;&gt;🔗&lt;/a&gt;&#xA;&lt;/h3&gt;&#xA;&lt;p&gt;TIL the origins of the concept of software waterfall development: it was first used to advise against the practice. There are a number of analogous examples of terminology for criticism being adopted by fans, either unaware or unswayed by the critic’s words.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
