13

This one is for @Fast-Nop

Both a rant and a joke/meme.

Its also funny because its true. Couple of teams (team responsible for orders and team responsible for accounting) are in seclusion in a meeting room right now cleaning up the web team's screw up.

Comments
  • 1
    TL;DR...the 'bug' was a new feature (already fully tested) scheduled to release on Tuesday (along with the DB/service changes). The two developers responsible thought a simple font change would be OK to release on Friday. I mean, why ask around? That would be silly.

    Its a great thing to have access to the changesets to see what actually happened vs. what is told to the 'powers that be' in order to cover your ass.
  • 0
    @PaperTrail That now makes me hungry for more details: What actually broke: the feature in spite of being tested or the font change screwed it up?
  • 1
    @phorkyas

    >That now makes me hungry for more details

    The feature was a change to how tax was calculated on promotions. The corresponding tax service was scheduled to be deployed also, so if they waited until Tuesday, everything would have been fine.

    Like a lot mistakes like this, the root cause is a lack of communication. This is not the first time the team has deployed a breaking change on Friday afternoon and no one knows about the bug until Monday. However, this is the first time real $$ has been lost.

    The "Oh shit..I have to cover my ass.." messages going back n' forth right now is so obvious (at least for me) and embarrassing.

    I literally want to chime in and say "Are you serious? You do know we can see the changesets, right? "

    Semi-good thing the details are too far into the weeds for our users to understand.
  • 1
    In a weird turn of events, the senior leaders got involved and had the manager remove the developer's name who released the bug in the internal inquiry documentation (too much into the weeds to explain that).

    They agreed it was inappropriate for the manager 'Dan' to "call out" specific individuals for a process problem and if anyone was to "blame", 'Dan' should have taken responsibility.

    There are days that this place is awesome.
  • 0
    @PaperTrail Yep, that sounds like a reasonable reaction. Fingerpointing is just shit. - Missing or failed communication ('processes') is such a common thing.
Add Comment