https://matt2ology.github.io/tags/uncle-bob/Recent content in Uncle-Bob on matt2ology Tech Journal and BlogHugo -- gohugo.ioen-usMon, 16 Mar 2026 04:30:31 -0700https://matt2ology.github.io/blog/brian-d-foy-random-adventures-note-taking-style/Mon, 16 Mar 2026 04:30:31 -0700https://matt2ology.github.io/blog/brian-d-foy-random-adventures-note-taking-style/<h2 id="i-like-brian-d-foys-random-adventures-note-taking-style"><a href="#i-like-brian-d-foys-random-adventures-note-taking-style" class="header-anchor"></a>I like brian d foy&rsquo;s Random Adventures Note Taking Style </h2><p>In contrast to my own &ldquo;literature&rdquo; note: <a href="https://matt2ology.github.io/literature/unitycoin-clean-code-uncle-bob-lesson-6-agile/">unitycoin clean code uncle bob lesson 6 agile</a> </p> <p>I like, Perl trainer and writer, <a href="https://www.amazon.com/stores/brian-d-foy/author/B002MRC39U?ref=ap_rdr&amp;shoppingPortalEnabled=true">brian d foy</a> – <a href="https://briandfoy.github.io/">Random Adventures</a> for his summary note of <a href="https://briandfoy.github.io/uncle-bob-lesson-6/"><em>“Coding Better World Together”</em> - Clean Code Lesson 6</a> . His notes are concise and practical, capturing the core ideas without unnecessary detail.</p> <p>In Lesson 6, <a href="https://blog.cleancoder.com/">Robert C. Martin</a> explains how many software projects suffer from classic symptoms of mismanagement: delivering the wrong product, producing low-quality software, or shipping late. These problems often arise from unrealistic expectations captured in the so-called <strong>“Iron Cross” of project management</strong>, trying to make a project <em>good, fast, cheap,</em> and <em>done</em> at the same time, even though in practice you can usually optimize for only three.</p> <p>Agile practices help teams confront reality early through data and transparency. Techniques such as <strong>story points</strong> and <strong>burn-down charts</strong> provide a measurable way to track progress. By putting these charts where the team can see them, everyone shares the same understanding of the project’s state.</p> <p>One striking idea from Uncle Bob is that <em>“the purpose of Agile is to destroy hope.”</em> That sounds pessimistic at first, but the real meaning is about exposing problems as early as possible. Instead of pretending everything is fine until the deadline arrives, Agile reveals how “messed up” a project might be while there is still time to correct course.</p> <p>The lesson also emphasizes small, focused teams working on small pieces of functionality. Estimation becomes easier when the team maintains a consistent reference task for assigning story points. Ultimately, a project is not considered finished when every planned task is completed, but when there is <strong>nothing valuable left to do</strong>.</p> <p>These ideas reinforce the core Agile mindset: transparency, early feedback, and incremental progress are essential for aligning software production with delivery expectations.</p>