Another Day, Another ID10T

Yesterday was filled with frustration. Filled. Chock full o'(going) Nuts. My javascript, which previously had been working like a little champ, decided to die just as my PM came to take screen shots and was giving me nice warm fuzzy words about how quickly I worked and what a good job I was doing. So yeah, that was kind of humiliating. (Humiliations galore!)

I spent the remainer of the afternoon (and ok, let's be honest, evening - and night while I tossed and turned trying to figure out the problem) trying to figure out what had happened. Cause you see, I hadn't changed anything.

Today, the problem was still there. (Not sure what latent polly-anna gene makes me think that I'm going to come back to work and it'll just *whoosh* be fixed, but somehow I still manage to do this on a fairly regular occurrence.) So I started to look at it and...well. Let's just classify this as another ID10T error. Long and the short of it is that I tested it with 0 and 1 file attachments, but never with more than 1. PM was like, "Ooh, let's have 4 or 5 so they can get a better picture of how it'll look" (which is a good idea since 4 or 5 is really more common than 0 or 1, but I didn't know that til yesterday too). Well, with 0 or 1 I can address the html tags by name, no problem. But when there's more than 1, you then have more than 1 html tag with the same name. Which, for those of you not asking yourself how I manage to call myself a software engineer when I make that kind of mistake, is a big "duh" situation. I could defend myself and say it's been a loooong time since I did any kind of serious web programming But...well...it was still just a stupid error.

So now, I am trying to find the best way to fix the problem and I think I'm on the right track and all is right with the world and, hey, what is up with the seriously spring-like weather we're having today??? 66?!

Anyway, beyond that I got my stitches out this morning and all looks well with my little gum graft so that is a good thing. And now I will return to my regularly scheduled programming. (Literally.)