Tag Archive: JavaScript

Dormant skills

I have a lot of dormant skills and interests. Really, I think that’s true of everyone. It’s just a matter of whether we acknowledge them or not. Back in the day I was sort of interested in web design. In the old job though it became a source of aggravation. I guess somewhere along the way I fell out of love. So why is my interest being awoken? I’m sure part of it is the new job and the fact that it uses some of these skills but in a less pressured way (thus far). Also, there are some improv-related ventures that I’m pursuing. As a stakeholder of one of the ventures I’ve taken it upon myself to play around with building a website. I’m making it sound important, but really it’s just an excuse to play around with my skills. I mean, I’m amazed at how much you can build with HTML, CSS, JavaScript, and JQuery. I’m not claiming that I’m one of those web-wizards that can code one of those tight pages that just flows. I’m not there yet, but I’m learning. I need to ride this wave of interest while it lasts.

Squished PITA

It turns out that the customer had a cached version of the old JavaScript file. Clearing her cache fixed the issue.

Booyah!

A scripting PITA

How do you debug something that you can’t reproduce? It’s really difficult isn’t it? Someone is experiencing a JavaScript-related bug on the site that I thought I had fixed this past week. No one in my team can create it. No one on the client end can create it either. Maybe the customer has a cached file? I dunno.

This is just so frustrating. Having to work on the task is sort of making me feel useless. I know otherwise. I know I’m capable–it’s just the issue that’s being a stubborn pain in the ass, or rather: a PITA (I love that acronym!).

Well, originally the issue was that there was a JavaScript error that was happening early on in the page specific to an older version of IE. That was causing the rest of the JavaScript on the page from being processed, preventing the customer from ordering. I found an issue and fixed it. In the QA phase the error wasn’t happening any more so the fix was pushed live. Now though? I don’t get why it’s happening again for one or two people that had reported it in the past. That’s why I’m suspecting the cache is the culprit. I have confidence in my fix! Well, I’m going to continue investigating, but I really don’t want to spend my whole day on this phantom of an issue. It’s going to affect my sanity if I keep at it.

Switch to our mobile site