5
Cruiser
7y

It was the end of my first week. Friday evening and everything was going well. I'd just made a career change and loved it. My new job, boss, and coworkers were fantastic.

So I decided to play a little with a portion of the website before leaving for the weekend. I needed to learn a module that was responsible for displaying our company hours online. I was told prior to being hired that this particular part of the site was important and the only recent cause of the previous developer working long hours.

It didn't work like I thought it did, and with changing one line of code, I brought the entire thing to it's knees. Not just the part displaying hours, but the entire page, which was our home page.

I didn't panic. I called some other devs I had met. I knew they could fix it. No one answered. 4.30pm on a Friday is not the best time to reach people. Four or five unanswered calls later, I started to panic. I tried changing the line of code back, but couldn't get it right. I tired removing the hours module, but that didn't work either. 10 minutes felt like an eternity.

I finally found the history feature of our CMS. It saves versions of pages and saved me that night. I rolled back to a version of the page last modified before I started working there, and it worked like a charm.

I didn't touch that module again until I had something to replace it with.

Comments
  • 2
    No dev environment? The do their dev work on the prod system?
  • 0
    There is, but I hadn't been shown it at that time. Which is weird, thinking about it now.
  • 0
    @Cruiser oh, ok. Where I work, the Dev role isn't allowed access in Prod, so we avoid that issue. Only Prod Support is allowed to do anything in Prod.
Add Comment