20 lines
828 B
Markdown
20 lines
828 B
Markdown
|
---
|
||
|
|
date: 2025-06-15
|
||
|
|
title: Is refactoring a lost art?
|
||
|
|
permalink: /daily/2025/06/15/refactoring-lost-art
|
||
|
|
---
|
||
|
|
|
||
|
|
How many people or teams take time to refactor their code?
|
||
|
|
|
||
|
|
Once the code is written and working, is it immediately considered done and not looked at again?
|
||
|
|
|
||
|
|
Or it is reviewed to check if it is as clear and readable as it can be?
|
||
|
|
|
||
|
|
Is it changed to be easier to change in the future?
|
||
|
|
|
||
|
|
How many open source projects have issues or merge requests for refactoring, or are they only focused on new features or fixing bugs?
|
||
|
|
|
||
|
|
Like writing automated tests, time should be invested in refactoring code.
|
||
|
|
|
||
|
|
Having cleaner code that's easier to read, understand and change in the future will make the tasks of future Developers easier and make the codebase easier to maintain and provide a solid foundation for future development.
|