|
James R. Twine wrote:
Anyone here that has been involved in software for more than 5 years must have seen or at least heard of a "perfect design" that got F-ed up by someone, somewhere
 I have yet to see a real "perfect design" from any business dept in my 5+ years. I believe they could screw up the requirements, specs, and design for a "Hello, world!" console app.
|
|
|
|
|
I wrote in "Too many external dependencies".
I suppose you could roll that into "Bad design" or lack of design. But nothing is more annoying than code that has a bunch of (unnecessary) dependencies. I wrote this to mean external dependencies - as in, say, operating system that I may not be able to upgrade, a component I don't have, a DLL that ends up crashing my system, etc.
But you could also take it to mean a lack of "loose coupling", so you have some module that can't be changed without needing to change 100 billion others.
An expert is somebody who learns more and more about less and less, until he knows absolutely everything about nothing.
|
|
|
|
|
as it should... all other problems are minor when working with a good design...
now, if you're working with a BAD design, then I dont care how pretty, well-commented, or speedy your code is... it's not going anywhere.
|
|
|
|
|
Of course, "bad design" is also the most subjective of the lot...
You're one microscopic cog
in his catastrophic plan...
|
|
|
|
|
no... i think "inneficient coding" is.
actually, inneficient coding is not subjective.. it's simply not specific enough.
I think it's pretty easy to differentiate between good and bad designs
|
|
|
|
|
How many times have you seen a developer take a vague requirement and start banging out code ?
It is hard to believe that there are still people who do not believe that a good design based on tangible business requirements is a prerequisite to successful software development.
Even for a small application the business requirement and design should still be done.
It is like saying you want to vacation in Hawaii, so you get in the car and start driving... only to arrive in California and realize you can't get there by car!
PJP
|
|
|
|
|
|
...that "inefficient coding" ranks up so high.
we are here to help each other get through this thing, whatever it is Vonnegut jr.
sighist || Agile Programming | doxygen
|
|
|
|
|
peterchen wrote:
...that "inefficient coding" ranks up so high.
I still don't know what the definition of 'inefficent coding' is.
Michael
CP Blog [^]
|
|
|
|
|
I interpreted as that the code would run inefficiently.
"If a man empties his purse into his head, no man can take it away from him, for an investment in knowledge pays the best interest." -- Joseph E. O'Donnell
The Second EuroCPian Event will be in Brussels on the 4th of September
Can't manage to P/Invoke that Win32 API in .NET? Why not do interop the wiki way!
|
|
|
|
|
|
I thought it to mean wasting resources - such as using a ton of memory, using slow algorithms, etc. - stuff that even a good optimizing compiler won't be able to fix. 
IMHO, I didn't vote for that option because these days it seems to be domain-specific. For desktop apps, efficiency hardly matters. But for servers or embedded apps, it is a big issue.
An expert is somebody who learns more and more about less and less, until he knows absolutely everything about nothing.
|
|
|
|
|
Navin wrote:
For desktop apps, efficiency hardly matters.
Hearing that is one of my pet peeves. That train of thought is one of the reasons most applications these days are so ridiculously bloated and slow.
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
Knowing efficient from inefficient coding is important. However, the old 90%-10% addage has moved to maybe 98-2. And inefficient investment of efficient coding is the one overall application killer - because most "efficient coders" rely on hacks that make code less readable, and often less portable.
we are here to help each other get through this thing, whatever it is Vonnegut jr.
sighist || Agile Programming | doxygen
|
|
|
|
|
peterchen wrote:
because most "efficient coders" rely on hacks that make code less readable, and often less portable
I strongly agree. From personal experience, I consider inefficient coding a symptom of poor code structure/architecture or a developer that is relatively new to the tech/language being used (assuming the developer is competent).
|
|
|
|
|
are my pet peeves. Especially when I find them in my own code 
Michael
CP Blog [^]
|
|
|
|
|
|
Absolutely
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
