News for hackers. Stuff that matters.
Re:Ignore details early on by zxcdw on Tuesday January 08, 2013 @04:14AM (#5025432)
Somehow you seem to assume that optimizing code would lead to complexity. From personal experience I would argue that often the code is actually clearer and more readable after it has been optimized. This is because great care has been put into it -- it's not just written and left at that, but it has been refactored with speed in mind.

Though my experience is mainly in C and C++, I guess it can be different in dynamic languages.

Re:Ignore details early on by calinet6 on Tuesday January 08, 2013 @09:44AM (#5026395)
There's a balance. You have to optimise to some degree (writing blatantly poorly designed code is just silly), but you shouldn't over-optimize. To me, that's sort of implied in the word 'optimize.' You should start with a good design, that's well-thought-out, and you should reduce it to the simplest and clearest possible concept, but you shouldn't go overboard until you know the path.
Re:Ignore details early on by ajanuary on Tuesday January 08, 2013 @04:44AM (#5025495)
You could just as easily soend that time refactoring for code clarity.