Re:The Economics of Clean Code
by bilekas on Tuesday February 11, 2020 @09:36AM
(#22298764)
> Juniors just thrash around from one design pattern to the next, never really achieving anything other than learning what doesn't work.
I couldn't put this into the words as well as you did, I know myself one of the turning points of realising I had become a better developer was learning from those who taught me how to identify the design patterns and how to build up requirements.
Clean code is usually less important than a good structure, if you have bad deverlopers or a lot of juniors, your processes should be in place to not allow them to go too far off course. This is what really improves the development time and the maintenance.
The messy code is usually localised to a small area and if a refactor is required, its much smaller.
I couldn't put this into the words as well as you did, I know myself one of the turning points of realising I had become a better developer was learning from those who taught me how to identify the design patterns and how to build up requirements.
Clean code is usually less important than a good structure, if you have bad deverlopers or a lot of juniors, your processes should be in place to not allow them to go too far off course. This is what really improves the development time and the maintenance.
The messy code is usually localised to a small area and if a refactor is required, its much smaller.