Episode 11: Avoiding Legacy Code with Michael Feathers

Avoiding Legacy Code with Michael Feathers
Follow us on Twitter! @techdoneright or leave us a review on iTunes and sign up for our newsletter (http://www.techdoneright.io/newsletter)!
Guest
Michael Feathers (https://twitter.com/mfeathers): Author of Working Effectively with Legacy Code (https://www.amazon.com/Working-Effectively-Legacy-Michael-Feathers/dp/0131177052); r7krecon.com (https://www.r7krecon.com/)
Summary
What makes a code base go bad and become "Legacy Code"? Can teams avoid writing bad code? Michael Feathers, author of Working Effectively With Legacy Code joins Tech Done Right to talk about technical debt, how communication can prevent bad coding practices, why coding problems are never just about code, and what it's like to go around the world seeing the worst code messes ever written.
Notes
02:36 - The Definition of “Legacy Code”
04:25 - What makes code bases go bad?
07:26 - Working as a Team to Avoid Technical Debt and Other Problems
09:49 - Tools and Techniques That Have Changed Since the Book was Written
scythe (https://github.com/michaelfeathers/scythe)
12:38 - Lack of Institutional Memory
15:24 - What creates technical debt?
- Scrum (https://www.scrumalliance.org/why-scrum)
- Extreme Programming (http://www.extremeprogramming.org)
22:50 - “Symbiotic Design”
- Symbiotic Design Provocation (https://www.r7krecon.com/provocation)
- Symbiotic Design Implications (https://www.r7krecon.com/implications)
- Conway’s Law (https://en.wikipedia.org/wiki/Conway%27s_law)
25:38 - Test-Driven Development
- Keynote - Writing Software (2014 TDD is dead from DHH) (http://confreaks.tv/videos/railsconf2014-keynote-writing-software)
- RailsConf 2017: Opening Keynote by David Heinemeier Hansson (https://www.youtube.com/watch?v=Cx6aGMC6MjU)
31:44 - Fads in Codebases
36:58 - Error Handling in Applications (in Relation to Conway’s Law) Special Guest: Michael Feathers.

Avoiding Legacy Code with Michael Feathers

Follow us on Twitter! @tech_done_right or leave us a review on iTunes and sign up for our newsletter!

Guest

Michael Feathers: Author of Working Effectively with Legacy Code; r7krecon.com

Summary

What makes a code base go bad and become "Legacy Code"? Can teams avoid writing bad code? Michael Feathers, author of Working Effectively With Legacy Code joins Tech Done Right to talk about technical debt, how communication can prevent bad coding practices, why coding problems are never just about code, and what it's like to go around the world seeing the worst code messes ever written.

Notes

02:36 - The Definition of “Legacy Code”

04:25 - What makes code bases go bad?

07:26 - Working as a Team to Avoid Technical Debt and Other Problems

09:49 - Tools and Techniques That Have Changed Since the Book was Written

scythe

12:38 - Lack of Institutional Memory

15:24 - What creates technical debt?

Scrum
Extreme Programming

22:50 - “Symbiotic Design”

Symbiotic Design Provocation
Symbiotic Design Implications
Conway’s Law

25:38 - Test-Driven Development

Keynote - Writing Software (2014 TDD is dead from DHH)
RailsConf 2017: Opening Keynote by David Heinemeier Hansson

31:44 - Fads in Codebases

36:58 - Error Handling in Applications (in Relation to Conway’s Law)

Special Guest: Michael Feathers.

Sponsored By:

Links: