Posts Tagged ‘tutorial’

I usu­ally use Scrip­ta­l­i­cious for my AJAX needs, but I’m working on a set of AJAX-ified forms on a web­site that’s already using jQuery, so I figure hey, it can’t be that hard to change over! Twenty min­utes later, cue the loud cursing and growling. I mean, the whole thing seems far more pow­erful, but every time I’ve wanted to start imple­menting it, I’ve been turned off by how com­plex it seems to do simple things. (Like slide down a div window, which I hope to have accom­plished before I turn 30. On a side note, I’ve been feeling old because I turned 25 today, until my little sister sent me a mes­sage saying that I’m “plenty young, for a pres­i­dent!” Which I sup­pose is tech­ni­cally true, so I don’t feel quite so washed up anymore.)

Anyway, back to my jQuery-induced headache: this very helpful thing to the rescue! If I can stop being dis­tracted by the gor­geous site design, I might be able to figure this stuff out, after all, without having to spend all day teaching my brain new methods of pro­gram­ming. I do so love pro­gram­ming tuto­rials written for designers. Thank you, pretty colourful website!

So, let’s say you’re having a problem with your email, or if you’ve found a bug in your web­site. Your first instinct, nat­u­rally, is to fire off an email to your trusty web-person. But wait! Before you hit send, make sure you’ve included as much detail as possible—what you were trying to do when the error hap­pened, what sort of error mes­sage (if any) you got, what soft­ware you were using at the time, etc. This will help your trusty web-person track down the problem far, far more quickly.

An excel­lent way of sup­ple­menting this infor­ma­tion is by sending along a screen­shot. I’ll often request this of clients when I can’t repli­cate a reported bug—if you’ve sent one to begin with, I can be that much more effective.

Here’s how you do it.
(more…)