Have you ever read a blog post about TDD, Dependency Injection, or some other concept and thought, “Sounds great . . . if you work in an ivory tower, but I have to work with [insert your code-base here].”? Or maybe you really like the idea but you have no clue how to start without beginning the project over? If you answered yes then Pablo is going to make you smile because this month’s topic is Refactoring ‘Brownfield’ Projects. Wikipedia has a fairly complete definition of Brownfield (http://en.wikipedia.org/wiki/Brownfield_(software_development)) but for our purposes you can consider any project that must use or take into consideration ‘legacy’ code a Brownfield project. What is ‘legacy’ code? Again, for Pablo this means any code that isn’t under test – including that lovely bit of code I just wrote . . . hmmm, I can’t wait to see what Pablo has this month.
If you haven’t already, please consider subscribing to the Los Techies Main Feed so that you can see the various post from all the Los Techies bloggers.
The main feed is here: http://feeds.feedburner.com/lostechies
As the month progresses you can expect posts on:
- PTOM – Brownfield Development – Making your dependencies explicit (Introducing DI and “poor man’s DI” )
- PTOM – Breaking Free of HttpContext
- Refactoring to TDD (putting a legacy system under test)
- Bringing an Inversion of Control container into the game
- Black-box analysis for replacing existing legacy apps
- Throwing out a Safety Net – using smoke tests to gain confidence your changes won’t break critical transactions
We’ll update this post with the links for these topics as they are posted so stay tuned and Enjoy!