Refactoring is a magic word commonly used by agile wizards to describe the process of transforming badly designed and badly written spaghetti code into a coherent beautiful part of nature’s creation using a few amazingly simple steps.

Originally used in Smalltalk, this term became widely spread in the software industry when more and more people around the world realized that it has a rather soothing effect on their managers, employees, and colleagues. No matter how uncomfortable someone was with the design or implementation of a piece of software, the sentence “we will refactor it later? seemed to make the issue sink into oblivion without no one having to change a single line of code. That, of course, saved a lot of valuable resources, enabling the production of more badly designed and badly written spaghetti code.

The book Refactoring: Improving the Design of Existing Code by Martin Fowler is considered the bible on Refactoring. Placing it in a visible location on your desk will officially make the 47$ you spent on it into the best investment you’ve ever made. It won’t make you rich, but it will buy you a lifetime of happy thoughts and no worries.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: