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."
Permalink for comment 536642
To read all comments associated with this story, please click here.
Eloquence
by Lennie on Thu 27th Sep 2012 09:13 UTC in reply to "better or not"
Lennie
Member since:
2007-09-22

Programming languages are like other languages if you ask me.

An experienced programmer is probably more eloquent in defining what he/she wants the code to do when using programming languages and he/she is also more likely to be more eloquent in the programming language of choosen.

An experienced programmer is also more likely to make better code, which is more generic or to the point and probably also better at choosing which code should be to the point or generic.

So an experienced programmer is more likely to make better code and because of the eloquence you also get shorter code.

This means shorter code (because of the programmers experience and knowledge) is usually faster and all the other properties you mentioned.

But hey, that is just my opinion ;-)

Reply Parent Score: 2