Let's do a major refactor right before a release, what could possibly go wrong? (:

EVERYTHING STOP

It ain't cool until you comment out your tests

“How hard can it be”..
3days later
Boss: “how could this happen!”

Nothing :) your throughtout tests suite will watch your back :)

Serious answer - put it in writing that you think it's a bad idea. At least that way you've covered yourself.

@AlmondSauce that's a good idea, unfortunately...too late for this round.

@amphair Worth bearing in mind for the future. I've turned around a fair few... shall we say heated conversations with various bosses using that technique. Turning from a "how the hell could you let this happen" to a "hold on a minute, I told you this would happen, here's the proof, why the hell did you ignore my advice" is very useful indeed.

Nothing, just go take a 2week vacation right after!!

Ideally your unit tests would give you the assurance that the code functions as it did before.

In the real world I'm currently 3 days into a simple 2 hour refactor

Is it Friday too?