Refactor: the tool should not be your process

In this talk I try to show that there's much more involved in refactoring a codebase and that the shinny new language we _really_ want to use should not be the primary vector for the process.

The slides are really simple and to better understand them I'd suggest following my speaker notes here: https://gist.github.com/rsoares/d5d38ba65077c726afe84af7da727bb3

Transcript

1. WHOAMI Ricardo Soares Independent software engineer @ BuzzFeed @botequilha on Twitter rsoares on Github
2. "FIAT LUX" "LET THERE BE LIGHT"
3. "LET THERE BE LIGHT" Requirements System Architecture Tooling
5. STANDING THE TEST OF TIME Your software is facing an ever changing environment, constantly evolving and adapting.
6. ADAPTATION FLOWS OF CHANGE
7. ADAPTATION FLOWS OF CHANGE Scalability ↔ Integration Security Biz Requirements
8. ADAPTATION AGENTS OF CHANGE
9. ADAPTATION AGENTS OF CHANGE Stakeholders ♀ Teams Individual Preferences
10. BLOCKERS
11. BLOCKERS ⏳ Time Humans Tech Debt
12. UNIVERSAL TRUTHS
13. UNIVERSAL TRUTHS ⿻ Flowcharts Language Primitives Meetings
14. ENDEAVOUR GETTING ALL TOGETHER
15. ENDEAVOUR GETTING ALL TOGETHER Holism Team and Stakeholders ▫ Micro-refactor ◻ Macro-refactor Communication Deploy!
16. REFACTOR THE TOOL IS NOT SHOULD'T BE YOUR PROCESS
17. THANK YOU!