Refactoring 2nd Edition: Chapter 3: Bad Smells in Code
Book cover copyright Martin Fowler
Overview
This chapter covers various “bad” practices that are a good indicator that you should refactor your code.
My One Takeaway
It’s a good thing the back cover has a list of these and what to do because it’s hard to know what to do with this list. It almost seems like there should be some kind of tool that looks for these. I’m not going to make it but it would be a good check.
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.
RSS
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