CLEAN CODE & REFACTORING
Four Reasons to Change your Software
Michael Feathers defines four main reasons to change your code in the book Working Effectively with Legacy Code. I found those few paragraphs interesting, and I would like to share them with you from my perspective.
Four main reasons to change are
- Adding a feature
- Fixing a bug
- Improving design
- Optimising
Adding Feature and Bug Fixing
The most typical reason to change software is an adding of the feature. Your software is acting one way, and the boss or client needs it to do something else.
At first, adding a feature may look like an easy task for both sides. Friction between the developer and the task assigner began when the assigner thinks it is a bug, but the developer sees it as a completely new feature.
At the moment when I am writing this article, I am also working on a form-based information system, and new task recently appeared in the mailbox. The client wants me to fix the focus behaviour of…
