• Solutions
    • I Can Help
      • Define
      • Educate
      • Integrate
      • Advise
    • Consultation
      • Assessments
      • Design Reviews
      • Code Inspections
      • Ongoing Support
    • Training Classes
      • Training Schedule
      • On-Site Classes
      • Online Training
      • Customized Coaching and Mob Facilitation
    • Learning Roadmap
      • Developer Essentials Training
        • Agile Analysis and Design Patterns
        • Hands-On: Extreme Programming Practices
      • Scrum Framework Developer Essentials
      • Design Pattern Developer Essentials
      • Object-Oriented Analysis and Design Patterns
      • Scrum Software Developer Essentials
      • Agile Software Developer Essentials
      • Agile Software Developer Intensives
    • Speaking
      • Beyond the Legacy Code Crisis
      • Five Developer Practices for Agile Software
      • Writing High Quality, CLEAN Code
      • Essential Scrum Developer Practices
      • Improving Your Scrum Process
      • The Agile Development Advantage
    • Testimonials
    • Clients
  • Resources
    • Blog
    • My Book: Beyond Legacy Code
    • Bibliography
    • Referral Program
    • Associates
  • Contact
    • Contact Me
    • Schedule A Call
    • About
  • Schedule A Call

Why I Wrote Beyond Legacy Code

  1. Home
  2. Blog
  3. Why I Wrote Beyond Legacy Code

2025 Public Training Schedule

June 23 26, 2025 – Agile Analysis and Design Patterns – Half-Day Sessions Online

July 22 – 25, 2025 – Agile Analysis and Design Patterns – Half-Day Sessions Online

Register Now
Or schedule a private class
Course Descriptions
  • Developer Essentials Training
    • Agile Analysis and Design Patterns
    • Hands-On: Extreme Programming Practices
  • Object-Oriented Analysis and Design Patterns
  • Scrum Software Developer Essentials
  • Agile Software Developer Essentials
  • Agile Software Developer Intensives
Follow me on Twitter:

Follow @ToBeAgile

Blog Post Categories
  • Announcements {19}
  • Articles {2}
  • Bits and Pieces {74}
  • Blogosphere {1}
  • Bonuses {2}
  • Build in Small Batches {27}
  • Collaborate {38}
  • Create CLEAN Code {34}
  • Implement the Design Last {11}
  • Integrate Continuously {30}
  • Off-Topic but Interesting {3}
  • Rants {82}
  • Refactor Legacy Code {24}
  • Say What, Why, and for Whom Before How {22}
  • Seven Strategies {38}
  • Specify Behaviors with Tests {17}
  • Write the Test First {27}
Archives
  • 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • 2022
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • 2021
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • 2020
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • 2019
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • 2018
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • 2017
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • 2016
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • 2015
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • 2014
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • 2013
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • 2012
  • December 2012
  • Privacy Policy

    (c) 2025 To Be Agile

    • January 13, 2016
    • Rants

    I wrote Beyond Legacy Code: Nine Practices to Extend the Life (and Value) of Your Software because I noticed two major disconnects in my experience as a developer. First, the more challenging technical practices such as test driven development and refactoring, were not being as quickly assimilated by teams as some of the simpler Agile practices like standup meetings and iterations.

    This is understandable because many of the technical practices are more advanced and although they represent the highest value practices in Agile they are easy to get wrong. When we do get them wrong we suffer greatly. I also noticed that in many teams, management didn’t really understand or value the technical practices so developers were not really being empowered to use them.

    Second, I wanted to demystify software development and make at least some of the ideas accessible to anyone. Do people outside the software industry really understand how software is created and maintained even though software affects all of us in profound ways?

    While software is radically different than the world of physical things we all live in, many of the ideas we’ve been developing in the software industry have a great deal of value for everyday life, and for other disciplines like science and even art. Software is the essence of our new society and it’s at the core of the information revolution. So the ideas are important but very difficult for people without the background to access, and that’s because software is a world in and of itself.

    One of the big challenges we face in our society both personally and collectively is the explosion of information that is coming at us all the time. It’s difficult to make rhyme or reason out of the barrage of data that constantly accosts us. Art, science, and the social sciences are also barraged with huge amounts of data. The reductionist aspects of science have helped us decompose ideas but at the same time it makes it very difficult for us to see the big picture.

    These are not varying concepts to software development. One of the biggest challenges we face in software is managing complexity, so we’ve built many techniques and tools to help us with that. These ideas are either directly or indirectly transferrable to other areas of our lives.

    I started playing with some of these concepts and discovered that I can explain them using some common terminology and some common sense.

    I read a lot of books on software development, many of them are good but many of them aren’t. And even the good software books can be challenging to read, so I wanted to write a book that was more accessible and would actually be fun and engaging to read.

    I also wanted to write a book that would change how people think about many of these technical practices and I know that in order to change people’s thinking and behavior, I’d need a lot more than just a series of facts. People learn through stories. They learn through anecdotes and metaphors and when we use these approaches, we often see people naturally taking up new behaviors. So instead of writing a technical treatise I decided to tell stories. The stories I tell come from my own experience working with thousands of software developers, and through these stories readers can see what works and what doesn’t.

    Everything boils down to common sense, even the most technical practices are based on common sense and so I try to boil down the technical practices to things that anyone can relate to. I have a lifetime of experience in the industry, and I’ve seen ideas come and go. I spent much of the past thirty years being frustrated, but over the last fifteen years or so, I have seen great progress being made.

    I have seen the practices that I discuss in my book both succeed and fail in the real world, and the key distinctions seem to be related to how well the purpose or context of these practices are understood by those who use them. So *Beyond Legacy Code* focuses on the reasoning behind the practices. There are principles that make them work, and we want to understand their purpose so we can apply them correctly.

    I remember in the late 70s people talking about how thinking computers were just a few short years away. We don’t talk about that much anymore because we realized we have no idea how to program our computers to approach many of the problems we deal with as humans. If anything, the last few decades have taught us how *little* we know and if we want to take computers to the next level, to do really interesting things, then we have to build software more reliably. And that won’t happen with the “cowboy coder” mentality that pervades our industry.

    Some people think that the practices of Extreme Programming (XP) are sort of a shoot from the hip approach to writing software but nothing can be farther from the truth. XP is a highly disciplined approach that requires a great deal of skill and focus. It’s not for beginners but when used correctly, it can be amazingly powerful way of building software.

    These practices are not for everyone or for every project. They work especially well for challenging projects or pioneering software development where we’re building things we have never built before. The industry has a long way to go and we have been making great strides. Agile has gone from a nice idea to the standard in software development today. But Agile was started by software developers for software developers and the heart of Agile lies in technical practices that have to be well-understood.

    This is why I wrote Beyond Legacy Code, to show that there are alternatives. The code we write is not inherently doomed to become legacy code that’s difficult to work with and hard to repurpose. If we pay attention to the forces involved in software development, to how things change and how we can adapt to change, then we can make our code far more adaptable. This will not only drop the cost of developing software but radically drop the cost of maintaining it.

    To learn more, read excerpts, watch a video, and purchase Beyond Legacy Code, visit http://BeyondLegacyCode.com.

    Previous Post: « How to Define a Successful Software Product

    Next Post: Why Nine Practices? »

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    Solutions

    I Can Help
    • Define
    • Educate
    • Integrate
    • Advise

    Consultation
    • Assessments
    • Design Reviews
    • Code Inspections
    • Ongoing Support

    Testimonials Clients

    Resources

    • Blog
    • My Book: Beyond Legacy Code
    • Referral Program
    • Associates


    Read my book!
    Schedule a Call

    Training

    • Training Schedule
    • Learning Roadmap
    • On-Site Classes
    • Online Training
    • Customized Coaching and Mob Facilitation

    Course Descriptions
    • Developer Essentials Training
      • Agile Analysis and Design Patterns
      • Hands-On: Extreme Programming Practices
    • Object-Oriented Analysis and Design Patterns
    • Scrum Software Developer Essentials
    • Agile Software Developer Essentials
    • Agile Software Developer Intensives

    Copyright 2025 © To Be Agile. All rights reserved. Privacy Policy.

    This website uses cookies to improve your experience. I'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
    Privacy & Cookies Policy

    Privacy Overview

    This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
    Necessary
    Always Enabled
    Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
    SAVE & ACCEPT