Ask Slashdot: What Makes Some Code Particularly Good?
itwbennett writes: When developers talk about what makes some source code particularly 'good,' a handful of qualities tend to get mentioned frequently (functional, readable, testable). What would you add to this list?
When it's mine.
Not being PHP would have to be in my top two list for what makes good code. Not being Visual Basic would be #1.
"Murphy was an optimist" - O'Toole's commentary on Murphy's Law
Lots and lots of GOTO NNNN and I know it's good code!
-The wise argue that there are few absolutes, the fool argues that there are no probabilities.
I think i can shed light on this subject, having several years experience in this field. New programmers and seasoned alike often make this mistake, either through carelessness or ignorance. When working to write good code, you must make sure to set good="yes" or good="veryyes." ive written code for 20 years now and this has only ever failed me in PHP. Apparently the language does not support "good" code.
Good people go to bed earlier.
If you have no rhyming variable names, then your code sucks. 1 stars
If you have one or two, it is barely acceptable. 2 stars
Half rhyme, then 3 stars.
If most, but not all, rhyme, 4 stars.
If every single variable rhymes with at least one other variable, you have a great job, 5 stars.
To get the coveted 6 stars, all the variable names have to rhyme with each other.
excitingthingstodo.blogspot.com
When it's written by a gender and race balanced team, in a positive, multicultural environment, then it's good code!
What if the comment is // this code sucks.?
Who ordered that?