Wednesday 7th May, 2014
9:00am to 10:00am
What are the four key reasons why software developers might be reluctant to refactor their code—even if they think refactoring is, at least in the abstract, a good idea? How might one effectively address those concerns?
These four concerns, and the means for addressing them, have applicability far beyond refactoring. In this talk, I'll discuss these lessons learned in a refactoring context and how they subsequently helped me as an architect and in other roles.
Architecture Lead (Corporate Internet Group) at JPMorgan Chase bio from LinkedIn
Sign in to add slides, notes or videos to this session