We do that. If we have to take a short cut we sit down with management and try to see if it's worth it.
We need to launch so we will do this now. We know January is going to be quiet so we plan to fix it then.
We need to launch so we will do this now. We know January is going to be quiet so we plan to fix it then.
If management is using it usually an attempt to shut discussion down in the context of (i) poor psychological safety on the part of devs because (ii) management doesn't trust anything the devs say because (iii) management knows that the devs are reading cargo-cult blog posts like "if this software was written in Haskell it wouldn't have any bugs".