Murphy’s Law

“Anything that can go wrong, will go wrong.”

Granted, I can’t say I’m cursed, unlike this wayward baseball team:


Today, with a mere 2.5 weeks left in our summer at ExtremeBlue, we’re enacting a code freeze on our project in preparation for a huge site-wide demo on Thursday, a site-wide Expo next Wednesday, and a national Expo in Armonk, NY on August 10-11.  By the end of the day today, all the major functionality that is in place will remain so (though we’ll take the next several days to polish things up, iron out bugs, and generally make the project ready for the eyes of the execs), and anything that hasn’t made it won’t ever.

So far, it’s been anything but uneventful, and it’s barely passed noon.

Lotus Notes

Actually, I have no issue with Lotus Notes itself.  The problem lies in one of the mail servers: as of this morning, my permissions on the server were mysteriously revoked, along with those of a few of my coworkers (the ones whose accounts are on the same server as mine).  Now, I can no longer access new emails or send anything out.  I’m cut off from the email world.  This isn’t a mission-critical issue, but it is awfully annoying nonetheless.

Dojo, Part 1

Again, no specific issue with Dojo itself.  I am attempting to port instant messaging functionality implemented in one website through Dojo over to our project.  I ran into problems (which wasn’t unexpected), so I created a more thorough testing environment to eliminate variables.

I’ve nearly cloned the environment in which the implementation works correctly, and it refuses to cooperate.  It’s behaving almost as though the codebase is hardwired to work only from this one specific file and nowhere else.  Which is completely contrary to how Dojo functions.

Dojo, Part 2

How in the BLOODY HELL does


work correctly in the first build, setting off a cascade of GET requests for REST-style logins, and yet in the second build it gets a 403 Forbidden error from the REST server?

WHAT THE %(@!*(!@#%#.

Oh, and the login actually works, according to the application server’s LoginHandler. Yet another communication breakdown: SOMEONE FORGOT TO BLOODY TELL DOJO.

Ugh. I need a lolcat.



About Shannon Quinn

Oh hai!
This entry was posted in lolcat, Programming, Real Life, Technology and tagged , , , , , , , , , , , , , , , , . Bookmark the permalink.

4 Responses to Murphy’s Law

  1. eksith says:

    Not to worry. If it doesn’t go wrong now, when it should, it will when it most certainly shouldn’t at all costs. Might as well keep the bottle of Excedrin (incidentally, my new best friend these days) at hand for the duration.

    Aaah the Bartman Incident. Boy, Alou was raving mad after he missed that catch.

    As for ol’ LN. They should have just stuck to Postfix, Dovecot and SquirrelMail 😉
    I know LN can do everything including serve breakfast in bed, but sometimes (*gasp* cliché) “less is more”.

    I’ve never worked with Dojo before, but it sounds like IBM has a particular affinity towards it. I imagine they didn’t settle on this overnight, so it must have some overriding advantage over others.

    Like, say jQuery? Have you done anything extensive with it or MooTools or Prototype?

    • magsol says:

      That is very, very true. I would much rather have had everything that could possibly go wrong actually go wrong then, rather than today when we do a live webcast demo for IBM executives all over the world. 😛

      I was both saddened and somewhat amused that Bartman had to go into asylum. In Florida.

      IBM has a whole department dedicated to expanding and integrating open source initiatives, and Dojo is near the top of that list. What they’ve done with it is nothing short of impressive. Nevertheless, they also make extensive use of all three of the other packages you mentioned.

      Amazing part is, our own project not only uses Dojo, but a second, differently-namespaced Dojo build, jQuery, and Prototype. Yep. Four JS libraries at once. Don’t ask why, it has something to do with legacy code that our summer project didn’t have time to refactor.

      (by the way, any insights as to why, every few months, I have to moderate and re-approve a comment of yours on my blog?)

      • eksith says:

        Good luck on the webcast!

        All this power being transferred to the browser means they want to take a whole new approach to building applications. Maybe somewhere up the food chain, there may be a new initiative toward the Cloud.

        I’ve had other blogs on hold my comments as well. Not sure why it happens. Could be a glitch or maybe because I don’t leave a lot of comments, the system may “forget” whether my profile is safe. After all WP prides itself on being the most “spam free” service out there.

      • magsol says:

        Thank you good sir! The webcast went flawlessly 😀

        I love how much is being done within the browser. I would be perfectly content to spend my life researching and implementing new and creative ways to push the limits of the traditional browser and continue the blurring between browser and desktop that has already begun.

        One word: CLOUD.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s