Any development project lasting for more than a year will inevitably need at least a few major refactors or even a complete re-architecture to keep a good development velocity sustainable. Those major changes are a joyous opportunity to introduce newer frameworks, coding patterns, and general architecture improvements. But, they can take a hefty amount of time without any positive results to show immediately. This talk will walk you through the best -and worst- practices I’ve seen over the years from both successful and unsuccessful efforts.
On the happy side, we’ll cover:
* Effective knowledge-sharing strategies for developers across the experience spectrum
* Personal strategies for building excitement and team buy-in
* Patterns for introducing new patterns quickly without overhauling the entire project
On the unhappy side, we’ll cover what happens when those break down:
* Isolated knowledge and going against framework best practices
* Losing team trust in yourself — or even the values of refactors
* Losing stakeholder trust in the value of refactors — or even the product
