31
amphair
5y

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

Comments
  • 5
    EVERYTHING STOP
  • 10
    It ain't cool until you comment out your tests
  • 4
    “How hard can it be”..
    3days later
    Boss: “how could this happen!”
  • 4
    Nothing :) your throughtout tests suite will watch your back :)
  • 3
    Serious answer - put it in writing that you think it's a bad idea. At least that way you've covered yourself.
  • 4
    @AlmondSauce that's a good idea, unfortunately...too late for this round.
  • 4
    @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.
  • 2
    Nothing, just go take a 2week vacation right after!!
  • 2
    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
  • 3
    Is it Friday too?
Add Comment