I just pushed source code accompanying my Refactoring in C# book to Github. Clone it here.
Refactoring support in Visual Studio 2010 lags miles behind refactoring support in in free tools like Eclipse or Netbeans.
Sometimes I hear YAGNI principle invoked in a way that it is clearly misinterpreted. For example “Maybe you do not need to refactor this code just yet” or “Maybe you do not need all those unit tests”. Thing is, to be able to do YAGNI, you need to have your code refactored and covered with tests. You need continuous integration and automated builds. Without these practices, once you need to implement a new feature in JIT fashion, things will inevitably start to break,
Developer Express have released another free C# tool that includes “a fresh selection of hand-picked features taken from CodeRush and Refactor! Pro.”
you can already order Professional Refactoring in C# and ASP.NET from Amazon and take a look at some excerpts from the book at wrox.com
It might sound funny to mention aesthetic qualities like symmetry when speaking about source code… It has to do with inner workings of our brain. These qualities are the way to communicate with fellow programmer on another level.
First of all, do not discard rewriting application from scratch without giving it a really good consideration. In my experience, it is often much easier to develop an application from zero when compared with refactoring legacy version; it is also much more difficult to refactor the legacy code than it might look at the first site. Do an experiment.
“Professional Refactoring in C# and ASP.NET” available with discount for pre-order at Amazon. A good catch for early birds 😉
Professional Refactoring in C# and ASP .Net is in the works!
“If It Ain’t Broke, Don’t Fix It”
Often portrayed as longstanding engineering wisdom, “If It Ain’t Broke, Don’t Fix It” posture only promotes complacency. Refactoring teaches against it, and for a good reason.