Tweet
As mentioned before, I work for a web hosting company as a Level 3 tech. Back when I was a Level 2 (specialized in scripting/programming support), we were sent an email about admins upgrading Ruby on Rails to version 2.3.2.
Horray. This generally means a massive inrush of customers complaining that our ghetto implementation of RoR broke things again when updated. This means another day or two doing nothing but devising a way to make the old apps work on the new version. 2 or 3 days later we get another massive rush of tickets into scripting about Ruby on Rails, but there had been no notice of an update from admins. I checked sites, and everything seemed fine and should be working.
SC: Smart Customer
Me: The badly misinformed
SC: I'm telling you that something's changed in your servers
Me: *thinking - how often do customers say that?* Sir, nothing has changed on our end. It MUST be on yours. This is unsupported and I cannot help further. *ends call*
...2 days later a coworker gets tired of the mess and goes to an admin. Apparently a senior admin quietly updated everything to RoR 2.3.3 and didn't tell anyone, not even junior admins. Yes, I called the guy back once we devised a way to fix the problem and profusely apologized for the bad info before, and even fixed his site for him as an apology. Sometimes I hate the (lack of) information flow around here.
Horray. This generally means a massive inrush of customers complaining that our ghetto implementation of RoR broke things again when updated. This means another day or two doing nothing but devising a way to make the old apps work on the new version. 2 or 3 days later we get another massive rush of tickets into scripting about Ruby on Rails, but there had been no notice of an update from admins. I checked sites, and everything seemed fine and should be working.
SC: Smart Customer
Me: The badly misinformed
SC: I'm telling you that something's changed in your servers
Me: *thinking - how often do customers say that?* Sir, nothing has changed on our end. It MUST be on yours. This is unsupported and I cannot help further. *ends call*
...2 days later a coworker gets tired of the mess and goes to an admin. Apparently a senior admin quietly updated everything to RoR 2.3.3 and didn't tell anyone, not even junior admins. Yes, I called the guy back once we devised a way to fix the problem and profusely apologized for the bad info before, and even fixed his site for him as an apology. Sometimes I hate the (lack of) information flow around here.