Successfully rewriting (or refactoring) a legacy system is a tricky and difficult task because there are no accurate requirements; just make it do what the current system does. Even if the original requirements documents are available it is almost guaranteed that they’re out of date and only describe part of what the system does. So what’s a developer to do?
Fortunately, that’s what this talk is about. You’ll learn a practical way of ensuring you know what the current system does, and that the new version (whether a rewrite or a refactoring) does the same thing. You’ll also learn how to prevent any systems you’re currently working on from having out-of-date requirements, without spending time updating the requirements document.
Burk is a long-time programmer and software architect, with experience in multiple languages including Java and JavaScript. He’s presented at multiple conferences including ConnectTech, DevNexus, JavaOne, and Oracle Code One, and contributed to two of the “97 Things” books published by O’Reilly.
Burk works as a Solution Architect for Daugherty Business Solutions where he’s focused on finding ways to deliver better code in less time, and teaching others how to do the same.
