Mon premier blog

Refactoring: Improving the Design of Existing Code Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke
Publisher: Addison-Wesley Professional

Certainly, I just realize how important it becomes when we maintain the code. After refactoring some code, make sure your test cases still pass and write new test cases where necessary. And you can be right saying that I've just read Refactoring: Improving. Image by seizethedave via Flickr You may say I've been reading a lot recently. Michael Wooten replied on Mon, 2011/10/31 - 12:29pm. Being part of this Don't use design patterns for the sake of design patterns: Good developers love writing crafty, intelligent code. By far the most important programming book I ever read was Martin Fowler's "Refactoring: Improving the Design of Existing Code". Refactoring: Improving the Design of Existing Code - Martin Fowler. This book should be treated as a classic in software craftmanship, and its contents are still relevant today as they were in 1999. The first place prize will be a copy of Refactoring: Improving The Design Of Existing Code, an Ubuntu Mug, an Ubuntu 10.04 LTS install disc, and a Mun pen. La semana pasada, para preparar decentemente la charla que impartí en Luce I.T., leí Refactoring: improving the design of existing code de Martin Fowler y Kent Beck. Over the past few months, I've been working with an Agile Team in two-week sprints improving an existing and quite complicated planning environment that my company has been developing over the past few years. Refactoring, I got influence when I read Martin Fowler's book on Refactoring: Improving the Design of Existing Code.