Andrew Stopford's Weblog

poobah

Sponsors

News

Articles

Family

Old Blogs

Browse by Tags

All Tags » Legacy Code (RSS)
Working with Legacy code #7 : The boy scout rule.
Uncle Bob outlines this concept well in in the 97 rules book. Leave the code a little cleaner than you found it In other words where you can improve and make better the code you are working in. In legacy code you should follow this concept with a blazing...
Working with Legacy code #6 : Technical Debt
I'm going to write more about technical debt at a later date but it is a subject also worth covering at a legacy level. Legacy code has a high level of technical debt by it's very nature, in following the series so far the debt is being managed and repaid...
Working with Legacy code #5: The blackhole.
Someone creates a class or series of classes for something, the classes are big in size with large complicated methods. The effort is a sea of technical debt for the entire team but in the thick of the daily chaos it is lost. With out the coder talking...
Working with Legacy code #4 : Remove the hard dependencies
During your refactoring cycle you should be seeking out the hard dependencies that the code may have, examples of these can include. File System Database Network (HTTP) Application Server (Crystal) Classes that service these kind (or code that can be...
Working with Legacy code #3 : Build a safety net.
The first port of call in changing legacy code is a safety net, without one your fingers will get burnt. Make your safety net a high level functional test over the major areas of the application. Automate the test, plug it into your CI builds and run...
Working with Legacy code #2 : Understand it.
In my last post I suggested drawing up a plan, the plan might be based on what you and the team already know of the code and your experiences so far in coding, fixing and refactoring attempts on the code base. Your plan might need further detail when...
Working with Legacy code #1 : Draw up a plan.
Blackfield applications are a minefield, reaking of smells and awash with technical debt. The codebase is a living hell. Your first plan of attack is a plan. Your boss (be that you, your manager, your client or whoever) needs to understand what you are...
Working with Legacy code
I'm going to start a series on working with legacy code based on some of things I have learnt over the years. First I define my terms for 'legacy', I define legacy as (as someone on twitter called it) not brownfield but blackfield. Brownfield can be code...
More Posts