Be the first to like this
There are lots of strategies for and discussions around dealing with huge behemoth legacy apps, but what about the people who wrote, maintain, and use them? What happens when the original "mess maker" is still at the organization where this code lives? What happens if she is your boss? How do you deal with the chaos of legacy code in an organization that still has the chaos of legacy People, Policy, and Work-Flow? This talk will discuss strategies to deal with people in the environment of legacy code. No matter how bad or good your code is, your problem is always with people. Let's talk about how to deal with them!