<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Jeff Bailey | Laws</title><link>https://jeffbailey.us/categories/laws/</link><description>This website contains learning resources, opinions, and facts about software-related technology.</description><language>en</language><generator>Hugo</generator><atom:link href="https://jeffbailey.us/categories/laws/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Mon, 30 Mar 2026 00:00:00 +0000</lastBuildDate><item><title>What Is Amdahl's Law?</title><link>https://jeffbailey.us/blog/2026/03/30/what-is-amdahls-law/</link><guid isPermaLink="true">https://jeffbailey.us/blog/2026/03/30/what-is-amdahls-law/</guid><pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate><dc:creator>Jeff Bailey</dc:creator><category>What</category><category>Computer Science</category><category>Software Engineering</category><category>Performance</category><category>Laws</category><description><![CDATA[<h2 id="introduction">Introduction</h2>
<p>You add more cores. The program gets faster. Keep adding, and gains shrink. Eventually, speed stops rising.</p>
<p>That ceiling has a name: <strong>Amdahl&rsquo;s Law</strong>. It gives the maximum speedup from parallelizing a program, given how much work must still run sequentially.</p>
<p>This matters because it prevents wasted effort. Teams add hardware expecting a linear speedup, then hit diminishing returns. Amdahl&rsquo;s Law explains why and points you to the bottleneck that actually needs work.</p>]]></description></item><item><title>What Is The Law Of Instrument?</title><link>https://jeffbailey.us/blog/2025/11/20/what-is-the-law-of-instrument/</link><guid isPermaLink="true">https://jeffbailey.us/blog/2025/11/20/what-is-the-law-of-instrument/</guid><pubDate>Thu, 20 Nov 2025 00:00:00 +0000</pubDate><dc:creator>Jeff Bailey</dc:creator><category>Software Development</category><category>Psychology</category><category>Development Practices</category><category>Laws</category><description><![CDATA[<p>Ever watch a developer solve every problem with the same tool? I&rsquo;ve seen teams use React for everything, even when a simple HTML page would work just as well. I&rsquo;ve watched developers unironically reach for Kubernetes to deploy a single-page app. I knew a developer who used a SQL Server database for <em>everything</em>. He stored the entire user interface definition in the database. He succeeded in tightly coupling the whole enterprise to SQL Server. He was enthusiastic about the power of this paradigm. He even considered creating the <strong>SQL MVC</strong> book.</p>]]></description></item><item><title>21 Irrefutable Laws of Leadership Summary: John Maxwell Book Review</title><link>https://jeffbailey.us/blog/2024/01/26/a-21-laws-of-leadership-book-review/</link><guid isPermaLink="true">https://jeffbailey.us/blog/2024/01/26/a-21-laws-of-leadership-book-review/</guid><pubDate>Fri, 26 Jan 2024 00:00:00 +0000</pubDate><dc:creator>Jeff Bailey</dc:creator><category>Leadership</category><category>Book Reviews</category><category>Laws</category><description><![CDATA[<p><strong>Quick Start:</strong> Looking for a comprehensive summary of John Maxwell&rsquo;s leadership principles? This review covers all 21 irrefutable laws of leadership with practical insights for leaders at every level.</p>
<p>I have a tenuous relationship with leadership.</p>
<p>The role of the President of the United States of America comes to mind when I think of high-stakes leadership. When I peer into that role, I wonder how narcissistic one must be to believe they are &ldquo;<em>the one&rdquo;</em> to lead well over 300M people to a better quality of life.</p>]]></description></item></channel></rss>