Comments on Doc On Dev: The Three "R"s of Clean Code

A set of nice easy rules like this will work, but ...

2010-12-18T19:44:45.675-05:00

A set of nice easy rules like this will work, but I think there're still a few more steps, such as training and code reviews. Training in what the steps mean. One person's idea of readable might be to write such concise code it's illegible. So, training which is the pre-stage and code-review is the post stage are vital.

Think about it from the point of view of a new team member coming in, what resources are there for that person to sit down and understand what it mean to write neat code.

anything that helps people remember gets my thumbs...

2010-12-10T12:31:04.387-05:00

anything that helps people remember gets my thumbs up.

Got to be careful though; condensing information runs the risk of generalisation, too much information is lost leading the reader to assumptions.

Have you ever used mind maps? These are pretty good for summarising things like this in an 'easy to recall' format while keeping associations between them.

The boy scout rule is fantastic and so simple, I l...

2010-12-07T17:45:26.276-05:00

The boy scout rule is fantastic and so simple, I like and will be using it and espousing it at every opportunity.
Having said that however, it is subjective and heavily dependent on the prime assumption of competency.
Great list.

Very nice! Why is "Descriptive Function Names...

2010-12-06T02:44:09.237-05:00

Very nice!
Why is "Descriptive Function Names" there twice?
I'd replace it in the "Reliable" section with
"Maintenance Free". That focuses programmers to really finish things and not to push unnecessary work over to the operations team.