My one-hundred-and-sixty-fifth podcast is up. Scott’s in Norway this week and he sits down with Michael Feathers. Michael is the author of "Working Effectively with Legacy Code." What is legacy code? Are you writing legacy code right now?
Hanselminutes Podcast 165 - Working Effectively with Legacy Code with Michael Feathers
Tagged with podcast michael feathers programming code legacy testing tests
Also huffduffed as…
-
Hanselminutes Podcast 165 - Working Effectively with Legacy Code with Michael Feathers
-
Hanselminutes Podcast 165 - Working Effectively with Legacy Code with Michael Feathers
Possibly related…
-
065 RR Functional vs Object Oriented Programming with Michael Feathers
Podcast: Play in new window | Download (Duration: 57:55 — 66.3MB) Panel David Brady (blog witter github ADDcasts) Charles Max Wood (twitter github Teach Me To Code Rails Summer Camp) James Edward Gray II (blog twitter github) Josh Susser (twitter github blog) Michael Feathers (twitter blog) Discussion Groupon Working Effectively With Legacy Code
http://rubyrogues.com/065-rr-functional-vs-object-oriented-programming-with-michael-feathers/
-
Java Pub House - Ep. 10 - Testing, Testing, 1.2.3
For those Unit Testers out there (and those who want to do more unit tests), this podcast is for you! We cover JUnit in general, and explain how to shoe-in unit tests in current (and legacy code). We talked about Dependency Injection (and the Concern of Creation), and Mocking (what it is, and how is it used). In all, if you ever wondered why creating unit tests in your current code is hard, or why are people talking about Dependency Injection (DI), come in, and listen!
-
James Whittaker | How Google Tests Software
One of the aspects of software development that has grown in importance is the need for quality testing of new products as part of the overall process. James Whittaker, co-author of How Google Tests Software, discusses how his former company built a successful model based on the vital testing of its new services. He reviews how testing has grown as part of development and the different testing roles that Google used. His points clearly show how developers need to consider the importance of testing as a role for the developer.