|
|
|
|
|
|
by guillemsola
976 days ago
|
|
|
I like this sentence as it's something business stakeholders can unddo. And even the article focuses mostly in refactoring it can be used with many other good habits. For instance monitoring has a price to set it, configure it... You can avoid part of the price by setting up a simple monitoring
It has a cost as you're not going to catch early on issues in prod. And the latter you realize something is no going well, the higher the cost will be to fix it, loss clients... And we can go on with many things as well, UX has a price, testing has a price, backups have a price... Hopefully the writer don't think he has found the final reason to justify why refactoring is a must as there are many other best practices were low price will imply higher cost at the end. Wasn't that what we used to call tech debt? XD |
|
|