<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: g6pdh</title><link>https://news.ycombinator.com/user?id=g6pdh</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 16 Apr 2026 19:30:26 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=g6pdh" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by g6pdh in "How NASA built Artemis II’s fault-tolerant computer"]]></title><description><![CDATA[
<p>A physicist who worked on radiation-tolerant electronics here. Apart from the short iteration loops, agile also means that the SW/HW requirements are not fully defined during the first iterations, because they may also evolve over time. But this cannot be applied to projects where radiation/fault tolerance is the top priority. Most of the time, the requirements are 100% defined ahead of time, leading to a waterfall-like or a mixed one, where the development is still agile but the requirements are never discussed again, except in negligible terms.</p>
]]></description><pubDate>Fri, 10 Apr 2026 08:25:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=47715179</link><dc:creator>g6pdh</dc:creator><comments>https://news.ycombinator.com/item?id=47715179</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47715179</guid></item></channel></rss>