Epic Fail or The Site is Down



  • @Lorne Kates said:

    Don't deploy new shit to the server after Wednesday, fucktard
     

    How about: deploy to staging, test it on there.

    If it passes sufficient tests, baseline production then deploy it.

    If it fucks up on production, roll back the release to that last baseline. Then determine why it worked on staging and not on production.

    The actual dates are pretty much immaterial. There just needs to be the right staff around at the right time.



  • @Lorne Kates said:

    Don't deploy new shit to the server after Wednesday,
     

    That's a bullshit rule. That's half the motherfucking week, you clitwrangler.

    No deployments on Friday is good enough.


  • Trolleybus Mechanic

    @dhromed said:

    @Lorne Kates said:

    Don't deploy new shit to the server after Wednesday,
     

    That's a bullshit rule. That's half the motherfucking week, you clitwrangler.

    No deployments on Friday is good enough.

     

    Well, argued, monkeylicker. Diff this shit into the slutslurping chart:

    [IMG]http://i.imgur.com/po7Y8EZ.png[/IMG]

     



  • @Lorne Kates said:

    Well, argued, monkeylicker. Diff this shit into the slutslurping chart:

     

    Fuck me felcher, that's motherqueefing git output, isn't it?

     



  •  @dhromed said:

    clitwrangler
    @dhromed said:
    Filed under: percussive maintenance
    On a completely unrelated note, pressing Ctrl+Shift+Down on a Gmail message window will add a citation level, Ctrl+Shift+Up will format as a list.

    I wanted to select lines of text using keyboard only and got frustrated. Didn't think of letting go of Shift at the time.



  • @Zecc said:

    On a completely unrelated note, pressing Ctrl+Shift+Down on a Gmail message window will add a citation level, Ctrl+Shift+Up will format as a list.

    Gmail also does this nasty thing now where it hijacks your up-arrow and down-arrow keys and re-purposes them to select individual email threads instead of scrolling the window (you know, what they do in 99.9999999% of other web applications.) I haven't figured out yet how to turn that "feature" off.

    Gmail is making all of the usability mistakes Microsoft made back in 1999, I find it kind of hilarious.


  • Trolleybus Mechanic

    @blakeyrat said:

    @Zecc said:
    On a completely unrelated note, pressing Ctrl+Shift+Down on a Gmail message window will add a citation level, Ctrl+Shift+Up will format as a list.

    Gmail also does this nasty thing now where it hijacks your up-arrow and down-arrow keys and re-purposes them to select individual email threads instead of scrolling the window (you know, what they do in 99.9999999% of other web applications.) I haven't figured out yet how to turn that "feature" off.

    Gmail is making all of the usability mistakes Microsoft made back in 1999, I find it kind of hilarious.

     

    Fucking arrow keys. The arrows seem to randomly work or not, at random, based on a random reason that is random.

    You can file a bug if you'd like your issue to be ignored or derided.

    Personally, I find it useful to use NoScript to block apis.google.com.  Odd that-- blocking Javascript INCREASES the usability of a site. :|

     



  • @Lorne Kates said:

    Fucking arrow keys. The arrows seem to randomly work or not, at random, based on a random reason that is random.

    I think in theory they added code where if you hold the key down, it'll scroll normally but if you tap it it'll select a message, but that code doesn't work. That's my guess at least.

    I love this FAQ page: "You can turn off all keyboard shortcuts except the ONE THAT ANNOYS YOU THE MOST AND EVERYBODY'S ASKING FOR A WAY TO TURN IT OFF! Fuck you, consumer!



  • I hadn't noticed the arrow key thing in Gmail TBH. It seems to work fine in messages. In message lists I usually scroll with the mouse.

    It annoys the crap out of me that they do that in the dying Reader though.



  • @dhromed said:

    @Lorne Kates said:

    Well, argued, monkeylicker. Diff this shit into the slutslurping chart:

     

    Fuck me felcher, that's motherqueefing git output, isn't it?

    That reminded me of this bot that looks through git commits on github, and posts all the ones with profanity in them.

    Assmunching shitstain.



  • @HoldYourHeadUpHigh said:

    I might have said, "Works for me!" as I was walking out the door.

    You, my friend, are one arrogant fucknard. I, for one, can certainly see why they canned you: it's because they started noticing that attitude.

    @HoldYourHeadUpHigh said:
    I still don't think it was a significant problem. If I cared and paid more attention, I would have noticed Bill freaking out and losing his shit. I didn't pick up on it because I didn't care until I was leaving and Bill caught up to me, finally explained why it was a big deal. After that point I sat down and hacked in a solution, so I could leave as soon as possible.

    So, blakeyrat was right: you went from not-a-big-deal to I-had-to-fix-it in less than a single paragraph. Either you, in retrospect, don't think it's a big deal, or Bill explained why it's a big deal (which would imply that you now do think it's a big deal). It can't be both.

    Except if Bill explained why it was a big deal, you realized from his viewpoint he was right, and then decided that his opinion was inferior to yours. Which is not only arrogant, but (more to the point) untrue. First of all the arrogance: you are both human beings. As blakey said, what's the big deal about staying for a few minutes and humoring your boss? It's Friday for him, too. He's losing his shit on a Friday afternoon, only to find you being a dick to him about it.

    Next the untruth: from your words, I deduce that you understood that it's a big deal to him for reasons that make some kind of sense. And the rub is, he's your boss. I understand that technically he's only paying you until 5 PM, but he's still paying you, and if he's got an issue that he thinks is important for reasons that are not moronic, then it is, because he is your boss. I'm not saying that's an infallible or always-valid argument, but in this case I think it holds up pretty decently.

    The response your boss get from me, would be a long sigh, because I would probably not be able to hold that in, and then a sort of friendly "well-I-suppose-I'd-better-get-cracking-then" look. Then I'd get cracking and fix it, leaving any other questions like: do I really have to do this, is this really such a big deal, why didn't you come to me an hour ago, etc to next Monday. This shows your boss: "he doesn't like being held in on a Friday afternoon with something tiny, but he's still going to fix it for me so I can stop losing my shit, and so can my customers". And that, is how we try not to get canned. To be fair, I have the benefit of hindsight and not being tired from a long week of work. Also, I am my very own walking set of WTFs because I would proceed to ponder this incident all weekend, working myself up and up and up, only to arrive at work on Monday, not raising any of those questions...



  • @toon said:

    @HoldYourHeadUpHigh said:
    I might have said, "Works for me!" as I was walking out the door.

    You, my friend, are one arrogant fucknard. I, for one, can certainly see why they canned you: it's because they started noticing that attitude.

     

    I think it's half the story, and we don't know precisely how he said it.

    I say "works for me lol!" all the time internally. The actual client-visible comment in the bugtracker is of course some polite variation of "unable to reproduce".

    What strikes me is that his superiors have sticks so far up their asses and the relationship between people of different departments in that company is so messed up that they can't deal with relaxed communication from a developer.

     



  • @dhromed said:

    I say "works for me lol!" all the time internally. The actual client-visible comment in the bugtracker is of course some polite variation of "unable to reproduce".

    And that is, I suspect, precisely where you and HoldYourHeadUpHigh are completely different. From how I pictured the story, his boss says: there's a bug here, and HoldYourHeadUpHigh replied: no there isn't. I always feel that assuming PEBKAC, as I suspect HoldYourHeadUpHigh did, is arrogant. Saying CNR and leaving it at that can be perfectly reasonable, but that's comparing apples and pears.

    Devil's advocate scenario. Let's say I'm his boss. If I were his boss, I'd simply see HoldYourHeadUpHigh go to the site, acknowledge that it is broken, and hit F5 to make the problem go away. And then turn around to tell me that my customers can "just hit F5", to fix a problem our company put into the site. So there's an urgent problem, I go see HoldYourHeadUpHigh about it, and because it will be weekend in a few minutes he refuses to fix it, basically telling me to just lighten up a little.

    Others have made many points about pushing changes on Friday etc etc, and I'm not saying his boss is right, or even not a complete moron, but if his boss explained it to his dad the CEO like I just pointed it out, it suddenly becomes a completely different story, regardless of who is right and wrong. And it didn't have to be if HoldYourHeadUpHigh had been a little more polite. But again, it was Friday, maybe he was tired or something. I guess I can't pick a side here, the story is biased towards HoldYourHeadUpHigh's side which is fine and perfectly understandable.



  • @toon said:

    @HoldYourHeadUpHigh said:
    I might have said, "Works for me!" as I was walking out the door.

    You, my friend, are one arrogant fucknard. I, for one, can certainly see why they canned you: it's because they started noticing that attitude.

    Hey, baby, but I can change.

    Sigh. Yeah, you are right. It took a long, long time to get to that point, like 8 years. I'm less likely to be fired for apathy now and I still wonder why past employers didn't fire me sooner. I am aware of my fucknard problem and when I can, I deal with it a lot differently.

    @toon said:

    @HoldYourHeadUpHigh said:
    I still don't think it was a significant problem. If I cared and paid more attention, I would have noticed Bill freaking out and losing his shit. I didn't pick up on it because I didn't care until I was leaving and Bill caught up to me, finally explained why it was a big deal. After that point I sat down and hacked in a solution, so I could leave as soon as possible.

    So, blakeyrat was right: you went from not-a-big-deal to I-had-to-fix-it in less than a single paragraph. Either you, in retrospect, don't think it's a big deal, or Bill explained why it's a big deal (which would imply that you now do think it's a big deal). It can't be both.

    I think Bill thought it was a big deal. Prior to these conversations, I didn't think it was a big deal. I am currently uncertain. I thought most people would simply hit F5, given the rate that errors in transmissions happen naturally (without a caching problem) when CSS doesn't load. I thought it was cool that the site still functioned even when most of the CSS was not loading correctly. I was informed later that I was incorrect. Given the site audience and their lack of technical acuity, I was, perhaps, being very optimist. Given that I haven't seen any data and studies done on whether or not a visitor will hit refresh (either key, set of keys or using the button), I still doubt the accuracy of that statement. Given the anecdotal evidence, it appears highly likely that I am wrong.

    To be fair, in past experience at the same company, when the exact problem popped up, it was an non-issue. When the same issue popped up a few weeks after my departure from the same company, the issue was "solved" by going to the boss and hitting F5. I expected F5 to exactly fix the problem. Also, from my perspective, I should have already been gone. Just because I stayed an extra 4 minutes, it was now my problem? How about calling up the person that actually caused the problem? What if the person who caused the problem stayed as long as I did? What if the person who caused the problem actually incremented the version himself? What if we didn't have a WTF system in the first place and it automatically sent the correct cache headers and/or to support IE6 incremented the version number based on the CSS build number?

    Part of the problem, from my perspective was that they implemented new processes and procedures that obsoleted the old without informing anyone. If you spent 3 years working for a company implementing WTF after WTF because they told you to implement WTF after WTF. Then one day, they actually care about appearances, what would you think? How nice it must be to work in a company where WTFs don't come in the form of communication and technological. I'm not saying I didn't screw up. However, my screw-up was communication. My expectation was that since this exact problem was always handled this way that it would always be handled that way. If they were concerned about the site cache problem, I would have implemented a solution which would have removed the problem from happening.

    Actually, I couldn't, because it wasn't "severe" enough to warrant spending resources on a "low priority" "non-issue". So, if you would please understand my frustration with my misunderstandings, then I would be most delighted.

    @toon said:

    Except if Bill explained why it was a big deal, you realized from his viewpoint he was right, and then decided that his opinion was inferior to yours. Which is not only arrogant, but (more to the point) untrue. First of all the arrogance: you are both human beings. As blakey said, what's the big deal about staying for a few minutes and humoring your boss? It's Friday for him, too. He's losing his shit on a Friday afternoon, only to find you being a dick to him about it.

    I wanted to anon, the post, so I changed the day. In reality it happen on a Tuesday. However, I use a quote from a Google engineer or it might have been attributed to someone else, "Your lack of insight does not constitute a priority on my part." Also, if it was a big of a problem, why wasn't I told sooner? Given the amount that the web site is used at the company internally, I would have thought it would have been reported long before 5pm, when it happened before 4pm. I also offered to spend time after I got home to work on the issue. Sure, it would have been 30 minutes, but what is 30 minutes? Nope. Marketing material went out that day to a couple of 70k people. More than likely if no one had checked the web site. Also, if he would have explained at the time that, "Hey, we sent a newsletter to 70k people and we think the CSS problem would affect our professionalism, could you fix it now?" As opposed to saying that after I about left and during the meeting where I was handed the final written notice.

    @toon said:

    Next the untruth: from your words, I deduce that you understood that it's a big deal to him for reasons that make some kind of sense. And the rub is, he's your boss. I understand that technically he's only paying you until 5 PM, but he's still paying you, and if he's got an issue that he thinks is important for reasons that are not moronic, then it is, because he is your boss. I'm not saying that's an infallible or always-valid argument, but in this case I think it holds up pretty decently.

    They would not have liked you. Since they were paying me by salary, they thought that it meant that if they wanted me to work 70 hours a week instead of 40, that it damn well entitled that to them. I know this, because they stated as much. I didn't have the heart to tell them that I would have jumped ship so fast I would have left an afterimage. Also during that same conversation, I was seriously contemplating saying, "Fuck this shit, I'm out!" and giving them the finger and not figuratively. I was silently telling myself, "Just 6 more months. Just 6 more months. Have to survive 6 more months."

    See above for the context. I only deduced that when he came in he was losing his shit based on hindsight. I included apathy because it has been a while and I really don't remember, so technically not a lie, just creative freedom given the length of time and my own memory. I am really terrible when it comes to people and their emotion state.

    @toon said:

    The response your boss get from me, would be a long sigh, because I would probably not be able to hold that in, and then a sort of friendly "well-I-suppose-I'd-better-get-cracking-then" look. Then I'd get cracking and fix it, leaving any other questions like: do I really have to do this, is this really such a big deal, why didn't you come to me an hour ago, etc to next Monday. This shows your boss: "he doesn't like being held in on a Friday afternoon with something tiny, but he's still going to fix it for me so I can stop losing my shit, and so can my customers". And that, is how we try not to get canned. To be fair, I have the benefit of hindsight and not being tired from a long week of work. Also, I am my very own walking set of WTFs because I would proceed to ponder this incident all weekend, working myself up and up and up, only to arrive at work on Monday, not raising any of those questions...

    That is good advice. I will try to remember it when in my head I'm screaming. Given that my normal state is to be a giant asshole, I'm unsure if I can actually pull this advice off. I guess it will take another being canned or two before it sinks in. Well, I'm in constant communication with my current boss and constantly asking questions about priorities and expectations. Also, given that I love my job and the people I work for, I wouldn't mind staying late. That may change within the next couple of years before my narcissism starts to kick in. I really wish there was a pill for that.


Log in to reply