Linked by David Adams on Tue 28th Jun 2011 15:35 UTC, submitted by HAL2001
Thread beginning with comment 479091
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Comment by MORB
by Soulbender on Wed 29th Jun 2011 16:05
in reply to "RE[6]: Comment by MORB"
Yeah, it's indeed much overused but it does apply in this situation. It's most often not wise to spend time and money designing for immense scalability before you launch. Try to make good engineering decisions that won't hamper you later on but don't sweat it until your userbase and traffic start to really increase.
RE[8]: Comment by MORB
by umccullough on Wed 29th Jun 2011 16:21
in reply to "RE[7]: Comment by MORB"
Try to make good engineering decisions that won't hamper you later on but don't sweat it until your userbase and traffic start to really increase.
Or to put it another way: "working properly" is usually more important than "working fast".
Once you have it working properly, at least it serves as a reference implementation which you can test further optimization against to make sure you didn't break anything.




Member since:
2011-01-28
Soulbender,
"Some wise guy said something about premature optimization a long time ago and it's still true."
I agreed with you up until this point. Too many people in CS use the quote above to justify designs with very poor scalability. Never forget that the quote was from the 1970s when the inefficiency typical of computing today was not yet conceivable. I'm afraid if modern day CS developers were sent back in time to work with Knuth, the quote you'd be reading would be quite different.