Refactoring agile fragile code is the gift that keeps on giving

<p>I&rsquo;ve been around the dev work block. There have been some good and fun projects. Then there have also been horror shows. But it doesn&rsquo;t matter what feelings I have towards the code, they all have one thing in common &mdash; they all need to be refactored, eventually.</p> <p>Refactoring is one of those facts of life for all developers. At some point, we all encounter it. There&rsquo;s no escaping and explaining the concept to upper management can be as equally challenging.</p> <p>For many non-techies, software is akin to an asset that&rsquo;s built and paid for. For the software developer, it&rsquo;s more like homeownership. At some point, the old pipes are going to leak, or you suddenly realize that building with asbestos was a bad idea.</p> <p>Even new builds come with their own set of issues.</p> <p>Nothing is perfect. You might love the color scheme and architectural plans, but to a different set of eyes &mdash; it might just be an overload of hedonistic maximalist self-indulgent code that only made sense to its creator.</p> <p><a href="https://medium.com/@PurpleGreenLemon/refactoring-agile-fragile-code-is-the-gift-that-keeps-on-giving-8126566e9d9d">Website</a></p>