> it’s simpler to rewrite part of the system than to even maintain it for a month.
This is often a career limiting decision. Rewrites are often much more difficult, particularly when you are dealing with a system that is not fully understood. This often leads to what should be a quick re-write taking > 3x more time and money than projected. In the end no one will remember why the technical reason for the rewrite, but they will remember who made the decision.
I've made this mistake a few times in my career, and I always thought, this project, it is the exception to the no-rewrites rule.
This is often a career limiting decision. Rewrites are often much more difficult, particularly when you are dealing with a system that is not fully understood. This often leads to what should be a quick re-write taking > 3x more time and money than projected. In the end no one will remember why the technical reason for the rewrite, but they will remember who made the decision.
I've made this mistake a few times in my career, and I always thought, this project, it is the exception to the no-rewrites rule.
reply