Not quite what I expected the talk to be - more about reverse-engineering a legacy system that nobody in your team has really been involved in. Fair speaker, and started well, but seemed to lose enthusiasm partway through.
Excellent talk, funny, well presented, engaging. Loved the use of comics in the slides, excellent talk. Some great content and links to tools. Check it out if slides/audio are available.
Great talk, amazing to see how much RM has changed his style since moving PlusNet -> iBuildings.
Loved the slides with the oldschool comics, great tools, great process advice. Will be making a lot of use of all of this shortly in my work.
Nice to see someone flying the flag for pragmatism, and testing, and good advice on what to do when you're forced to produce more legacy code based on old legacy code.
I will definitely be yoinking the term 'Technical Debt' to use in conversations with management.
Great talk, excellent slides. I really appreciated the straight forward check lists given for each stage of preparing and dealing with the legacy code.
Definitely useful points to feed back to our client services team as to what resources they should be looking at getting hold of at the start of a legacy project.
Really great talk that covered pretty much all aspects of dealing with legacy code. It was well presented with great slides, and from now on when I'm dealing with a soul-destroying timebomb of a bloated legacy system I can dream of all the docs that just couldn't be found or tools couldn't be practically implemented.
Comments
Comments are closed.
Not quite what I expected the talk to be - more about reverse-engineering a legacy system that nobody in your team has really been involved in. Fair speaker, and started well, but seemed to lose enthusiasm partway through.
Second time I've seen it, still good. Like the slide designs and the pragmatism.
@dmi isn't that what's in the title and abstract? This is what legacy code is, and the way to deal with it.
Useful content / tools mentioned. Thanks
Excellent talk, funny, well presented, engaging. Loved the use of comics in the slides, excellent talk. Some great content and links to tools. Check it out if slides/audio are available.
Excellent talk with plenty of useful and practical tools and examples presented. Thanks.
Very nice talk about handling working with older code, lots of practical advice which is always a plus!
Nice, good guidelines on working with legacy code, well presented and structured. Some good quotes too!
Good speaker, well presented, simple slides and lots of useful suggestions.
Ace speaker, easy to listen to, good reinforcement of concepts using comics :)
Good talk, great slides and lots of humor. Nothing new to me buddy :D
Great talk, amazing to see how much RM has changed his style since moving PlusNet -> iBuildings.
Loved the slides with the oldschool comics, great tools, great process advice. Will be making a lot of use of all of this shortly in my work.
Nice to see someone flying the flag for pragmatism, and testing, and good advice on what to do when you're forced to produce more legacy code based on old legacy code.
I will definitely be yoinking the term 'Technical Debt' to use in conversations with management.
Great talk, excellent slides. I really appreciated the straight forward check lists given for each stage of preparing and dealing with the legacy code.
Definitely useful points to feed back to our client services team as to what resources they should be looking at getting hold of at the start of a legacy project.
Thanks!
I now realise how much I hate crap legacy code: even a well presented talk by a charismatic speaker upset me.
Great talk - really covered everything in a really engaging way!
Really good talk. Great slides and well presented. Good job.
First half was a bit obvious (reading docs, etc) but second half with practical examples of dealing with code was much more useful.
Really great talk that covered pretty much all aspects of dealing with legacy code. It was well presented with great slides, and from now on when I'm dealing with a soul-destroying timebomb of a bloated legacy system I can dream of all the docs that just couldn't be found or tools couldn't be practically implemented.
Still, we can but try!