There are three groups of people around every legacy system - those who are stuck with it, those who don't want to be with it, and those who love it and see its value. How do we reconcile these three opinions and rewrite legacy code without completely replacing it?

Today we talk with Dave Thomas. Dave is an all-around player in the software industry with vast experience as an executive, investor, board member, consultant, architect, and engineer. He is Chairman of Bedarra Corp, which provides consulting on technology and business strategy for emerging technology, products, and services. He tells us what the drivers of legacy innovations are, why he thinks refactoring is a "little lie" of the modern software industry, and how to approach modifications in less-than-ideal situations.

When you finish listening to the episode, connect with Dave on LinkedIn and visit his website at www.davethomas.net.

Mentioned in this episode:

Dave Thomas on LinkedIn at https://www.linkedin.com/in/davidathomas/

Dave's website at https://www.davethomas.net/index.html

Badera Corporation at https://www.bedarra.com/

One of the reasons why it is difficult to work with legacy code is the lack of preserving the contextual reasons for past coding choices.

Today we talk with Chelsea Troy, a Machine Learning Team Lead at Mozilla and a computer science lecturer at the University of Chicago. She tells us about the value of code review in the software-building process and why code review should not be treated solely as a mechanism for approval.

When you finish listening to the episode, visit Chelsea's website at https://chelseatroy.com.

Mentioned in this episode:

Chelsea's website at https://chelseatroy.com

Mending code while it is running is risky. One wrong move and a small change can bring the entire system to a halt.

Today we talk with Edward Hieatt, Chief Customer Officer at Mechanical Orchard, a GenAI native company that modernizes critical legacy applications without disrupting what they are doing. He tells us how to use AI to identify system dependencies, why it is important to first understand data flow before diving into code, and how to maintain functionality during the modernization process.

When you finish listening to the episode, connect with Edward on LinkedIn.

Mentioned in this episode:

Edward on LinkedIn at https://www.linkedin.com/in/edwardhieatt/

Mechanical Orchard at https://www.mechanical-orchard.com/