Question

This question already has an answer here:

My manager has tight deadlines to meet.

The current project I am working on is currently on schedule, but I've noticed a couple of quite significant areas in the code that are really badly written. (Bits of code get called two or three times, when they only need to be called once.)

The problem is, as far as my manager is concerned, the program works. As he sees it, there's no point making lengthy changes to code that will make us miss the release date, for no tangible improvement that he can see. He keeps saying "That's not a priority. It's working fine as it is."

Should I keep trying to persuade him, or should I just do what he suggests and leave it? Why or why not? Note that how to persuade management has already been covered.

No correct solution

Licensed under: CC-BY-SA with attribution
scroll top