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 536929
To read all comments associated with this story, please click here.
RE: The Best Code
by emrehliug on Sat 29th Sep 2012 00:57 UTC in reply to "The Best Code"
Member since:
2009-12-27 a futile metric. Sure there's good code and bad code, but it draws focus away from the solution itself and nit-picks at the implementation. Often times the developers are hired/contracted to implement totally asinine solutions for any given problem. The best code in the world isn't going to be appreciated by the users if the solution doesn't work for them.

Who is good code important to? It's important to us as developers. But in my experience users & clients don't care, at least as long as the developer is able to manage the mess (which isn't always a given).

Agreed. In my experience, good code is code that gets the job done. If there is interest, money, and time enough to attempt to reach the other milestones - readability, maintainability, simplicity, speed, etc. - then I'm certain that good code can become better, maybe best. But users, clients, or managers, might not even notice that because they - more than often - don't care about those things we, as developers, care.

Reply Parent Score: 2