Refactoring 2nd Edition: Chapter 2: Principals in Refactoring
Book cover copyright Martin Fowler
Overview
This chapter: 1. What refactoring is 2. Why you should refactor 3. When you should refactor 4. Problems with refactoring
My One Takeaway
Under the section “What Do I Tell My Manager” there’s this quote:
Of course, many managers and customers don’t have the technical awareness to know how code base health impacts productivity. In this cases I give my most controversial advise: Don’t tell! Page 55.
I’ve worked for places where this is absolutely the case and think “Don’t Tell!” is good advice but you might have to hide the refactoring inside a deliverable.
Scott Keck-Warren
Scott is the Director of Technology at WeCare Connect where he strives to provide solutions for his customers needs. He's the father of two and can be found most weekends working on projects around the house with his loving partner.
Top Posts
- Working With Soft Deletes in Laravel (By Example)
- Fixing CMake was unable to find a build program corresponding to "Unix Makefiles"
- Upgrading to Laravel 8.x
- Get The Count of the Number of Users in an AD Group
- Multiple Vagrant VMs in One Vagrantfile
- Fixing the "this is larger than GitHub's recommended maximum file size of 50.00 MB" error
- Changing the Directory Vagrant Stores the VMs In
- Accepting Android SDK Licenses From The OSX Command Line
- Fixing the 'Target class [config] does not exist' Error
- Using Rectangle to Manage MacOS Windows