We'll be watching Modern Legacy Systems
(
http://www.infoq.com/presentations/net-java-legacy-techniques) at
Graham Lee's suggestion because:
- It explains how systems can become legacy
- It incorporates the political/social aspects in addition to the
technical, which I always find interesting
- It’s extra-relevant if we discuss the Feathers book suggested below :)
Graham advises that the slides don't add much, so feel free to just
grab the MP3 from that page and skip the video.
We'll ALSO be reading the next block of Feathers' Working Effectively
with Legacy Code:
Block 2: The FAQs and nothing but the FAQs:
* Chapter 11: I need to make a change; what to test? (Effect Analysis)
(20 pp.) (Jeremy W. Sherman, Stafford Brooke)
* Chapter 15: My application is all API calls (9 pp.)
* Chapter 17: My app has no structure! (Naked CRC) (12 pp.) (Jeremy W. Sherman)
* Chapter 20: This class is too big, and it needs to stop growing (23
pp.) (Brian Hardy)
Don't like this stuff? Vote in the next poll, and add your own
suggestions to
http://j.mp/bnrbc-texts!
We only had 4 voters this last time, so your vote really well and
truly does matter.
--
Jeremy W. Sherman
+1 (314) 488–0053
Software Engineer
Big Nerd Ranch
bignerdranch.com |
twitter.com/bignerdranch |
facebook.com/bignerdranch