Linked by Thom Holwerda on Wed 26th Sep 2012 23:25 UTC, submitted by MOS6510
General Development "Having read this, one realization is that better code often means less code. I don't think about lines of code exactly, or something similarly stupid, but in terms of meaningful code. However, argument for less code isn't about making code as compact as possible, avoid redundancy, etc. The argument is about not writing code at all whenever reasonable or possible. Should we focus on deciding what should and what should not built instead of polishing our software development craft then? Yes and no. Yeah, I know. Exactly the kind of answer you expected, isn’t it? Anyway, you can't answer this question meaningfully without a context."
Thread beginning with comment 536692
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Eloquence
by Alfman on Thu 27th Sep 2012 19:56 UTC in reply to "RE[2]: Eloquence"
Member since:


That's the problem, these are nice abstract ideologies but they're meaningless in practice since everything is relative. Write as much code as you need, but no more! Well, that almost goes without saying, but it doesn't acknowledge the evolutionary processes that software undergoes to get from A to Z. Like others have said, sometimes more code is better than less, there are so many factors that need to be considered (ie modular versus hardcoded, efficient vs simple, quickly hacked together vs long term managability). It would be ignorant to push forward an absolute ideology up front without even taking into account the specific requirements of a project.

Reply Parent Score: 3