3 ms·

The author of the tweet does a fanstastic job explaining the bug. He wrote a bunch of follow up tweets in reply to his orginal tweet.

• tomc1985 8y ago
  And he spends way too long with his crappy version of storytelling before he gets to the point
  • soneca 8y ago
    He also explains that he wrote that 5am from an hospital. From my point of view, he was just venting his frustrations making a point of how old the error origin was. It was not "storytelling", he was not writing it with the main goal of "getting to the point" so you could benefit. Calling it "crappy" sounds unfair and mean to me.
    • tomc1985 8y ago
      It is crappy in the sense that it is yet another person repeating the same tired trope of highlighting just how supposedly egregious some issue is in context of arbitrary events that happen to share the timeline. I am sick of this sort of temporally-oriented futurism as it betrays the writer's inexperience in actually shipping code and I am sick of amateurs being taken seriously in this field. Yeah, its an old issue, obviously nobody cared enough to fix it until now, STFU... edit- and finally, its twitter. stick to the character limit, or put it in a blog post. (and maybe this should be my last beer :)