Monday, August 20, 2012
I am a huge proponent of writing quality code, a view that is shared by many of my colleagues. Unfortunately, I do encounter those who do not share my enthusiasm. Their view is often one of “Get It Done,” whereas I take the position of “Get It Done Right.” When discussing refactoring, the “Get It Done” developer often brushes it aside as a waste of time.
I want to address that crowd, and anyone else who eschews refactoring, with my top 5 reasons why you should refactor your code.
5. Your Code Sucks
Broken Bridge / jollyUK / CC BY
How often do you write an...