*pouts*

BugAsk us instead and/or in addition to.

Or just provide thoroughly wrong answers that cause things to break.

Annoyingly, my carefully written email to the IT dude designed specifically to keep me from looking like a flake ended up making me look like a flake, because he followed all my steps and it ended up working for him. I have no idea why it didn't work for me in the first place.

Stupid computers.

I'm a writer! I write! I do not write XSL! XSL does not count as writing!

Or just provide thoroughly wrong answers that cause things to break.
posted by eamondaly 21 December | 14:56

Hahaha, yeah and perfect that wide-eyed "What?!" look. Way better than a 'told you so'.

Not that I endorse passive aggressive behavior, but there's a big difference between being untrained in something technical and ignorantly passing those duties on to someone without seeing first if they're qualified.

Annoyingly, my carefully written email to the IT dude designed specifically to keep me from looking like a flake ended up making me look like a flake, because he followed all my steps and it ended up working for him. I have no idea why it didn't work for me in the first place.

On preview, you must be one hell of a writer! =D

See! Yes! This is what my job is *supposed* to be, writing up the steps that other people follow to get correct results! I *am* good at that! :)

I'm "qualified" in the sense that I'm smart enough, and logical enough, to keep soldiering through until I make it work, but I'm not qualified enough to fix a lot of the problems that pop up without help from the IT department. Which, really, seems unfair to them, because they didn't sign on for this project, which is why I hate bothering them when I run into roadblocks.

Hm. Wanna switch jobs?

If you have enough of this to do, it might behoove you to download something like an eval copy of Komodo, or at the least look into using something like XML lint to catch basic syntax problems.