in reply to Don't Blame The Browser

Monks, I must repent. I blamed the browser, but the fault was my own. QA reported to me that after accessing a particular page in Krang a few times IE would get really slow and then crash. This page has a lot of Javascript on it, so I figured it was probably another IE Javascript bug.

Hunt and Thomas' book The Pragmatic Programmer has a section on the general case of this tendency, which they call "select isn't broken". The gist of it is: if there's a bug, it's probably in your code, not the browser, window manager, operating system, or what have you. Not always true, of course, but good to keep in mind.

Excellent book, btw.

--
F o x t r o t U n i f o r m
Found a typo in this node? /msg me
% man 3 strfry

Replies are listed 'Best First'.
Re^2: Don't Blame The Browser
by drewbie (Chaplain) on Jun 11, 2004 at 04:44 UTC
    You reminded me that I need to get that book off my wishlist and onto my bookshelf! Perhaps there will be a copy at YAPC... I've only read good things about what they have to say. I recently read their new version control book, and it's a good introduction to the concepts behind version control, branching, etc. Not quite a meaty as I had hoped about branching & merging, but adequate nonetheless.
Re^2: Don't Blame The Browser
by water (Deacon) on Jun 12, 2004 at 23:19 UTC
    The bug is never in MY code. Nope. Never. Hasn't happened once.

    I just wish they'd get around to fixing select and IE which are messing everything up -- those slackers.

    <g>