Typical Workflow

August 01, 2011

1. Create awesome Javascript function.
2. Test in Browser X; function works as desired.
3. Test in Browser Y; function does diddly squat.
4. Call Browser Y names.
5. Question Browser Y’s parentage.
6. Start angry blog post about how Browser Y should be written onto thousands of usb drives and airbombed over enemy countries to destroy their ability to use the Internet.
7. Get distracted from completing blog post while searching Wikipedia for appropriate WWII bomber references to link into post, start WWILFing, and end up obsessing over Jack Churchill after learning about his habit of taking longbows and claymores into battle during WWII.
8. Create generic version of code to insert into blog post to show how Browser Y’s sole purpose for existing is ruining my day.
9. Notice slight issue with code that points to incorrect usage of a function on my part.
10. Fix problem.
11. Discover the code now works as desired on Browser Y just perfectly.
12. Quietly delete blog post while making mental note to reference Jack Churchill later.
13. Wonder how the hell Browser X was operating as desired with incorrect implementation of code.
14. Drink heavily.

This entry was posted on Monday, August 1st, 2011 at 1:45 pm and is filed under javascript. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

12 Responses to “Typical Workflow”

  1. Bradley said on August 1st, 2011 at 1:51 pm:

    I’m still fairly confident Browser Y’s mother was involved in a drunken night of debauchery in some poorly lit IRC channel.

  2. Antoine Butler said on August 1st, 2011 at 1:52 pm:

    Wait, you drink heavily on step 14? What happened to cursing browser X for putting you in a false state of security? Looking at you Firefox.

    *Takes a drink*

  3. Missy said on August 1st, 2011 at 1:53 pm:

    This is just too spooky for words… perhaps we were separated at birth. As for so-called ‘smart’ browsers that automatigically close tags (or just ignore that they’re broken) and make up code as they go along, I sometimes wonder if life would be easier if we all went back to using Mosaic.
    On second thoughts, I’ll go and wash my mouth out.

  4. Anna said on August 1st, 2011 at 1:55 pm:

    Awesome. This has made my day!

  5. Kristoffer said on August 1st, 2011 at 2:07 pm:

    Get. Out. Of. My. Head.

  6. Chris Jean said on August 1st, 2011 at 2:33 pm:

    15. Still gripe about Browser Y because it truly is terrible, just not for this reason.

  7. Aaron Holbrook said on August 1st, 2011 at 3:57 pm:

    Haha that’s fantastic Kyle. Thanks for making me go look up Jack Churchill…

  8. Rachel Nabors said on August 1st, 2011 at 6:39 pm:

    And this is why haters who blame browsers for their subpar code skillz get no cred.

  9. JON STIEGLITZ said on August 2nd, 2011 at 3:36 am:

    Awesome. Basically encountered regularly in web design. Thanks for making me laugh. Not so much for making me drink.

  10. Liz said on August 2nd, 2011 at 6:13 am:

    You think that’s bad, try developing a HTML-based mobile app!

    You get to go through the entire process several times:

    1) the html/css/js code in a simulated mobile browser

    B) PhoneGap on simulator (assumes simulator works as indicated on the label)

    III) on hardware

    Lather (foam at mouth?) rinse, repeat

  11. Ryan Corradini said on August 2nd, 2011 at 6:39 am:

    HA! Done this countless times; it’s funny because it’s true.

    Welcome back, by the way. It’s been a long summer.

  12. SeanJA said on August 2nd, 2011 at 8:55 am:

    You don’t test your code in browser Z?