We can all agree that bringing old projects back to life is never easy. So when you’re archiving a project, think of your future self and leave some exploding breadcrumbs.
Sometimes, getting old projects running again can be a real pain. Thankfully, doing a smidge of prep work while archiving a project will go a long way toward bringing the project back.
Debugging legacy applications is, in general, no fun. In this post, I’ll describe a helpful tactic: wrapping a unit test around the questionable code.
Very few people enjoy debugging legacy applications.† Here’s one concrete, super-handy tip to make it a quicker, less painful process.
What does a potted plant have in common with a large software codebase? At first glance, they seem like completely different things. But in fact, both require regular maintenance to stay healthy and keep growing. When they’re neglected, both begin to decay in much the same way. I take care of the dozen plants distributed […]
Do you know about the --ignore-matching-lines option to GNU diff? I recently found a great use for it… We were tasked with comparing large sets of XML documents for a web service product. The project called for a SoapUI testsuite using Groovy scripts to compare complete SOAP responses against files containing the expected responses.
In the last few weeks, customers and potential clients have asked me on several occasions how Test-Driven Development relates to legacy code (incidentally, one fitting definition for legacy code is code having no test suite). As much as we all might like to throw out legacy code (especially when it’s craptacular) and “do it right”, […]