Reputation
5,908
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
14 28
Newest
 Necromancer
Impact
~291k people reached

Mar
24
comment Turn away a bug if no reproducible test case exists?
@seansilver: If it's a real bug, it'll turn up again. Otherwise, if you can't narrow it down, you're going to be running in circles.
Mar
24
comment Turn away a bug if no reproducible test case exists?
+1: I don't know how these other people fix things...
Mar
24
comment Turn away a bug if no reproducible test case exists?
Seriously? "I had a bug, and I can't replicate it! Fix it!!!" And your response is to do...what? If it can't be replicated, by the customer or the programming staff, how can it be fixed?
Mar
24
comment Why bother with detailed specs?
@nikie: I'm certainly glad that all your bosses and customers are willing to bow down to your holy judgement about what features are to be allowed in the software that you are graciously designing for them. Indeed I am so inspired by your disdain of design documents, that, from now on, I am only going to design pong-clones, and tell them that that is what is specified by the seeecret design document that I keep in my head.
Mar
24
comment Why bother with detailed specs?
@nikie: Must be nice.
Mar
24
answered Optimizing web applications
Mar
24
comment Why bother with detailed specs?
@nikie: Tell it to the Duke Nukem design team. You have to deal with QA, marketing, phbs who read too many magazines...It still matters.
Mar
24
awarded  Good Answer
Mar
23
awarded  Nice Answer
Mar
23
answered Why bother with detailed specs?
Mar
18
answered Good interview programming projects
Mar
18
answered How do you answer “Rate yourself” questions?
Mar
18
comment Harmful temptations in programming
In my environment, there are two major sites. Either one can originate a request for code, but the code will end up being deployed to both. They're different enough that you have to tune the code a bit for each...The practical result is that one site always gets beta code, and the other site always gets polished code, but then we never have time to migrate the polish back to the other site. I have had a number of people complain about our "uneven" code, or alternately, people at one site complaining about a program that people at the other site think is perfect.
Mar
17
comment Are `break` and `continue` bad programming practices?
@sjoerd: What it does is tell whoever is reading the code that the break conditions aren't in the loop header. It's not ideal, but it's functionally identical to the original posters code.
Mar
16
comment How was programming done 20 years ago?
@slomojo: In 1991? You know the first NT windows came out in 1993, right? Netware was popular until NT 4 started gaining traction in the late 90's. Of course, proprietary Unix crushed both of them in terms of usage, but still.
Mar
16
awarded  Nice Answer
Mar
15
answered Is the “One Description Table to rule them all” approch good?
Mar
15
comment How was programming done 20 years ago?
@Thorbjørn : We had the coffee pot cam! And usenet! What else do you really need? Honestly, from my recollections, it wasn't that much of a problem. The need for web documentation has increased with the complexity of the stuff you're creating. If you were hammering together an accounting application with a text gui, you didn't need much documentation.
Mar
15
comment How was programming done 20 years ago?
@tmn: Heh. I don't like those either, for pretty much the same reason...Of course, I don't need to use them either, not being a web guy. 4GLs were worse though, because they were proprietary. Support cost a fortune, and if you didn't have support, you couldn't upgrade. I looked into a new license for ours a few years back, so I could migrate everything to a new server environment, and the license ran 150k! Per site! The COBOL I could migrate for free, and the databases only required some $500 interface. Whole project shut down because of that goddamn proprietary 4GL environment.
Mar
15
answered Bugs vs. Nonexistent Features