The Twitter thread:
All I can say here is that I try to lead by example. If there’s a clear path to “make the change easy, then make the easy change,” make sure the commit history shows that explicitly, then ask for a code review even if your process doesn’t require it. 1/ https://t.co/VDxDbEQUf3— Sam Livingston-Gray (@geeksam) June 9, 2019
Sam Livingston-Gray - F̶l̶u̶e̶n̶t̶ Refactoring Talk: Sam talks about refactoring a gnarly Rails controller method. This is a lightly edited version of a talk Sam gave in 2013.
21:47 - Refactoring Resistance: Who are you trying to convince?
- Product Owner (Goal Donor)
- Funder (Gold Owner)
- Crusty Teammate
- Newbie Teammate
28:57 - The Risks of Refactoring
- Technically Viable
- Organizationally Viable
- A System Capable of Improvement Over Time
3 Different Kinds of Technical Debt:
- Intentional Debt
- Evolutionary Debt
- Bit Rot
35:08 - Documentation and Decision Records
36:59 - Code Value Judgement
42:00 - Convincing Coworkers Re: Refactoring a Codebase
Coraline: Adaptive Capacity.
Sam: It’s about dealing with people and effectively working with and for them.
To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.
Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks!Support Greater Than Code
This episode of Greater Than Code is brought to you by Atlas Authority. Atlas Authority helps organizations manage and scale their Atlassian stack. With expertise in Jira, Confluence, Bitbucket and other software development tools, Atlas Authority offers consulting, training, licensing and managed hosting services. Visit AtlasAuthority.com/GTC to find out more and learn why organizations trust Atlas Authority to implement, support, and maintain their critical Atlassian applications.