Survey Results

FirstPrev Next

Re: No fast code? James R. Twine15-Jun-04 7:23 James R. Twine 15-Jun-04 7:23     Man, you have GOT to meet some of the developers I have had the... um... pleasure of working with, or see some of the code that I have seen!!!    Makes me weep...    Peace! -=- James Tip for SUV winter driving survival: "Professional Driver on Closed Course" does not mean "your Dumb Ass on a Public Road"! Articles -- Products: Delete FXP Files & Check Favorites Re: No fast code? peterchen15-Jun-04 7:32 peterchen 15-Jun-04 7:32  ok, you get condolences.. we are here to help each other get through this thing, whatever it is Vonnegut jr. sighist || Agile Programming | doxygen Re: No fast code? James R. Twine15-Jun-04 7:53 James R. Twine 15-Jun-04 7:53  Thanks! -=- James Tip for SUV winter driving survival: "Professional Driver on Closed Course" does not mean "your Dumb Ass on a Public Road"! Articles -- Products: Delete FXP Files & Check Favorites Re: No fast code? Chris Maunder15-Jun-04 6:33 Chris Maunder 15-Jun-04 6:33  Most often I hear "Wow - this thing is really broken" cheers, Chris Maunder Remember that a lone amateur built the Ark. A large group of professionals built the Titanic. Bug free code? KevinHall14-Jun-04 9:02 KevinHall 14-Jun-04 9:02  Is there a real product out there that is completely devoid of bugs? Bug-free code only exist's in Walgreen's fictional city called "Perfect". Maintainable code is well... maintainable. When bugs are reported, the code is easy to modify. Maintainable code should (in theory anyway) be easier to extend as well, and easier for other people to read. Unless you are looking for optimizations (fastest code or code that uses the least resources), maintainable code seems (to me anyway) the most logical goal. Re: Bug free code? Anonymous14-Jun-04 17:04 Anonymous 14-Jun-04 17:04  we don't talk about "perfect" bug-free ... i think the good IDE would prevent user from making bugs ... agree ? Re: Bug free code? Tim Smith14-Jun-04 17:14 Tim Smith 14-Jun-04 17:14  No, not by a longshot. I can just see the IDE trying to figure out if you really wanted "2*r*3.14159" or "r*r*3.14159". Tim Smith I'm going to patent thought. I have yet to see any prior art. My perspective ian mariano14-Jun-04 8:57 ian mariano 14-Jun-04 8:57  I said "All of the above -- writing CORRECT code." That pretty much encapsulates all of the provided options. When writing code, above all it must solve the need in design behind the code and follow the stated options, in other words, it should be correct. Each developer may come up with equally valid and correct code. Elegance is nice, but that can be sacrificed for optimization, robustness and extensibility. Measure twice and cut once [Design], play well with your environment, always have an error strategy, and above all have fun :P Ian Mariano - Bliki | Blog "We are all wave equations in the information matrix of the universe" - me The only possible answer Gary Wheeler14-Jun-04 8:11 Gary Wheeler 14-Jun-04 8:11  IMO, the only possible answer is 'bug-free code', since that phrase encompasses the other attributes listed. Software Zen: delete this; Re: The only possible answer Navin14-Jun-04 8:13 Navin 14-Jun-04 8:13  Bug-free code? What's that? I actually wrote in, "Code that people will buy". You know, you can invent the greatest, bug free, most maintainable code in the world, but if nobody wants it, what good is it? "Fish and guests stink in three days." - Benjamin Franlkin Re: The only possible answer Anthony_Yio14-Jun-04 15:47 Anthony_Yio 14-Jun-04 15:47  That is in fact the most crucial requirement for a success or failure of a project. However, it should by right be done before coding phase like system study and survey. Sonork 100.41263:Anthony_Yio Re: The only possible answer Blake Miller14-Jun-04 9:28 Blake Miller 14-Jun-04 9:28  I disagree. I selected "Code that can be understood by others" figuring if there were bugs, or it was too slow, or it had to be extended, or nearly anything else, that could be done by someone else if necessary. Re: The only possible answer Tim Smith14-Jun-04 17:12 Tim Smith 14-Jun-04 17:12  Goes hand in hand with maintainable. Tim Smith I'm going to patent thought. I have yet to see any prior art. Re: The only possible answer Chris Maunder15-Jun-04 6:35 Chris Maunder 15-Jun-04 6:35  I disagree. Bug free != efficient, fast or easy to maintain. Sure, you can put those attributes in the requirments doc, but if they aren't satisfied are they bugs or merely unimplemented features? cheers, Chris Maunder Remember that a lone amateur built the Ark. A large group of professionals built the Titanic. Re: The only possible answer Gary Wheeler15-Jun-04 7:36 Gary Wheeler 15-Jun-04 7:36  I'll weasel a little here based on wording. I was interpreting the phrase 'bug-free' as being equivalent to 'defect-free'. In the corporate culture where I work[^], defect-free encompasses extensibility, maintainability, understandability, performance, and resource efficiency. An application that doesn't meet at least 'acceptable' levels in all of these areas will fail to meet the end user's requirements or expectations in some way. For our production-oriented customers (a surly lot), failing to meet their needs/wants/vulgar fantasies is Not A Good Thing. Software Zen: delete this;

Last Visit: 31-Dec-99 18:00     Last Update: 25-Apr-24 14:13 Refresh ᐊ Prev1234567

General    News    Suggestion    Question    Bug    Answer    Joke    Praise    Rant    Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.