What I took from Spolsky article wasnt that you shouldn't touch X/Y/Z, but that you should approach new code in the simplest and quickest way you can. I have o

What I took from Spolsky article wasnt that you shouldn't touch X/Y/Z, but that you should approach new code in the simplest and quickest way you can. I have often been guilty over engineering things to do them the "right way", to either end up throwing the feature out anyway or having to reengineer because I didnt know enough about the problem to fulfill its design from the outset anyway. while prototype fast is a reasonably mundane point, Its still one we get wrong time and time again, and I think programmers pay lip service to it as an ideal, but when it comes to actually having to leave that nasty bit of code alone because it does its job, too often we go down the wrong path of making it "right"