Discover the challenges of inheriting a two-decade-old codebase and the complexities of software archaeology. Explore how understanding the past can affect current practices, and learn about the tension between maintaining functionality and dealing with poor code quality. Delve into the pitfalls of legacy systems and the concept of drift, revealing how historical context shapes modern expectations. This engaging discussion reveals insights for developers navigating the murky waters of outdated technology while keeping well-being in focus.
13:33
forum Ask episode
web_stories AI Snips
view_agenda Chapters
menu_book Books
auto_awesome Transcript
info_circle Episode notes
question_answer ANECDOTE
The 20-Year-Old Codebase
Brian inherited a 20-year-old codebase from a solo developer.
The code was useful but lacked quality, clarity, and tests.
volunteer_activism ADVICE
Ask Why, But Never Answer
Acknowledge bad code, but avoid dwelling on the "why."
Focus on solutions instead of assigning blame.
volunteer_activism ADVICE
Don't Assume Code Makes Sense Today
Don't assume code works the same way it did years ago.
External factors can change how code behaves (like the Macintosh capacitor example).
Get the Snipd Podcast app to discover more snips from this episode
What do you do when you inherit a 20 year old codebase? In this episode, Squirrel and Jeffrey look at an extreme example of legacy software and discuss why it's important to understand past contexts as well as address modern discrepancies.
Links:
- Brian's Archaeology Tips: https://www.linkedin.com/pulse/10-tips-software-archeologists-brian-reich-n0ase
- Ask Why, But Never Answer: https://blog.jbrains.ca/permalink/ask-why-but-never-answer
- Macintosh's Backward Capacitor: https://www.downtowndougbrown.com/2024/11/the-capacitor-that-apple-soldered-incorrectly-at-the-factory/
--------------------------------------------------
You'll find free videos and practice material, plus our book Agile Conversations, at agileconversations.com
And we'd love to hear any thoughts, ideas, or feedback you have about the show: email us at info@agileconversations.com
--------------------------------------------------
About Your Hosts
Douglas Squirrel and Jeffrey Fredrick joined forces at TIM Group in 2013, where they studied and practised the art of management through difficult conversations. Over a decade later, they remain united in their passion for growing profitable organisations through better communication.
Squirrel is an advisor, author, keynote speaker, coach, and consultant, and he's helped over 300 companies of all sizes make huge, profitable improvements in their culture, skills, and processes. You can find out more about his work here: douglassquirrel.com/index.html
Jeffrey is Vice President of Engineering at ION Analytics, Organiser at CITCON, the Continuous Integration and Testing Conference, and is an accomplished author and speaker. You can connect with him here: www.linkedin.com/in/jfredrick/
Troubleshooting Agile 