Save Big On Open-Box & Used Products: Buy "Beyond Legacy Code: Nine Practices to Extend the L...” from Amazon Open-Box & Used and save 19% off the $38.00 list price. Product is eligible for Amazon's 30-day returns policy and Prime or FREE Shipping. See all offers from Amazon Open-Box & Used.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Beyond Legacy Code: Nine Practices to Extend the Life (and Value) of Your Software 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
Special offers and product promotions
About the Author
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top customer reviews
Non technical people as well as technical people will be able to come away with not only how developing software could be improved but how to improve working together in cross functional teams. I believe it is a good book to provide agile teams.
Reading through Beyond Legacy Code, it reads like the numerous tutoring sessions David has delivered to me. Simple and practical coding advice for those with deep technical skills, and even those with light technical skills such as project managers. David has a deep understanding of the Agile value proposition and speaks to the specifics in a way that any team member can comprehend.
In all, a superb book I recommend to ever company and team I coach. You can gain some level of value from Agile with minimal focus on code, but if you want to be "great" you need to follow David's advice to extend the life and value of your software.
Among many other important topics, the author strongly emphasizes the need for quality, maintainable code. Something which many of us are the biggest victims of. Especially those bosses/mangers who think they got a good deal as they've pressed their dev team and got them to agree to a shorter time-frame. Well, that's gonna come back to bite them (us) later. As smart developers we must have standards for ourselves and not (always) succumb to these kinds of pressures. True, our bosses/managers might find someone who'll agree to do it quicker and they'll have their opinions of us for the short time, but ultimately we will prevail as it'll become clear and evident that our code is robust, understandable and easily maintainable. Of course we have to use our best judgement and decide on a case-by-case basis how much it's worth investing in the quality of the project.
I have come to realize the great benefits of Agile in terms of team cohesiveness, managing expectations, good communication, rapid development and quality code that is maintainable . As discussed in this book, many teams say they are agile while they truly miss the main points of agile and the only resemblance is that they stand while they have their daily meetings :). Agile has become the buzz word that all software teams and companies describe themselves as practicing as they know it's good marketing but 90% of them are totally not Agile. Even for those teams that are really invested in being Agile are still not truly on point, some of the founders of agile say that the agile practiced today is far away from the Agile they have created and therefore don't reap a fraction of the benefits they theoretically can.
It's important to understand the use of the phrase "Legacy Code" in the title. As soon as you finish a piece of code and move on to the next task, it's legacy code - and everything from that point forward is maintenance. And as the author points out, maintenance costs far outweigh code creation. The nine practices the author spells out are designed to increase code quality in the first place and accordingly, reduce subsequent maintenance expense of the code you've written before.
But more than a list of software development best practices, the reason for the 5 stars is the way in which they're explained and substantiated. David's conversational style and the context he presents along side the advice given make the information easily digested by programmers and managers alike. As an individual that serves both roles, I find the book can be taken as a whole, painting a complete picture and as reference material.
Similarly, this book is accessible to the entire team -- from managers to analysts to developers. It's written with both technical and non-technical audiences in mind, and Bernstein achieves his goal.
This book has gained a spot on my "must read" list, along with Uncle Bob, Martin Fowler, and Michael Feathers.