9

Global variables destroyed my day

Of course you can call me a bad programmer and all. When you have the idea, sometimes globals make it seem easy, accessible and "saving resources". They are devils.

The app was connected to a suite of applications. So I ended up silently destroying it neighbors. I committed and pushed the shit. Just when the testers made their weed high smoke tests, a server stopped working.

I got an email that boss wanted the latest version, I reverted the wrong branch, which had code unrelated to its name, pushed shit again and voila.

I went to the bathroom and laughed. I had to take a smoke. I'm still laughing while typing this. The damage is too much and I can't help it. I'll go home, leave this pc on and work remotely through the night. It might be the hysterics speaking now, but I messed up, and I need magic by friday morning.

Comments
  • 3
    Edit: All this happened while I was listening to Fire in Bone by The Killers, on loop, non-stop, since 9:30am
  • 3
    Sending thots and prayers your way
  • 13
    Please use // prefix in your global variable name.
  • 2
    @fnf47 nice comment
  • 0
    Why exactly doesnt your company keep backups?
  • 0
    As a QA I love globals. Easy target, big returns. They always provide a solid foundation of issue reports to fallback in case something sneaks through.
Add Comment