Code Rot Is a Process Decision

<p>I&rsquo;ve had the great fortune to work for an organization that made a good-faith effort to empower its teams. And I&rsquo;ve worked at other places that didn&rsquo;t.</p> <p>In my role as a dev lead, therefore, I&rsquo;ve seen firsthand the difference between the two: empowered and&hellip; what&rsquo;s the opposite of empowered? Not exactly disempowered, more&hellip;&nbsp;<em>unpowered</em>.</p> <p>&ldquo;Unpowered&rdquo; because there&rsquo;s no &lsquo;oomph&rsquo; to it. It constantly needs to be prodded and pushed. It won&rsquo;t move by itself.</p> <p>What do I mean by that? Let&rsquo;s talk about the way unpowered organizations affect technical work.</p> <p>Oh boy. So many topics to choose from &mdash; ineffective use of resources; poor documentation; a lack of meaningful ways to improve the process from below.</p> <p>But I&rsquo;m a dev lead. I&rsquo;m coming at this from an engineering perspective. Most books and articles on the empowered process don&rsquo;t look too deeply into how it directly improves the engineering process.</p> <p>I&rsquo;m here to rectify this situation. But to understand how empowerment propels us forward, we must first understand how a lack of empowerment holds us back.</p> <p><a href="https://betterprogramming.pub/code-rot-is-a-process-decision-d4b37cf1e26b">Website</a></p>
Tags: Code Technical