Laufeyjarson writes…

The suggestion in this one was very simple, “Code in paragraphs.”  Deceptively simple, because it means different things to different people. (more…)

The Best Practices tell us never to place two statements on the same line.

In general, I agree with this, and find it a workable thing to do.  There’s a few cases I forget, or decide not to.  In most of them, it comes back to bite me later, and I wish I’d listened.

At the end of the day, I like whitespace, so yes, use a new line.

The PBP suggests using spaces to indent all code lines, instead of hard tabs.  The hard tab character should appear nowhere in a file.

I disagree with this, but have given up the argument and simply do it anyway.  I feel it a minor loss, and not worth the confusion it causes from people who don’t understand hard tabs. (more…)

The PBP suggests using four space indentation levels.

The book goes into many reasons for this.  It suggests that I’m an “ancient coding master” because I learned with eight columns, and find that a perfectly acceptable number.  Cue; GET OFF MY LAWN!  =) (more…)

The PBP suggests using a 78-column line length.

I’m good with this.  I don’t feel the need to be a pedant about it, but I like the idea in general. (more…)

The suggestion is to put a comma after every value in a list, even the last which doesn’t need it. (more…)

The suggestion here is to place a semicolon after every statement.  I agree with this, even if it isn’t technically needed.  The only place I’ll skip it is if it is a function returning a constant value, and that’s all that is in the function, like this: (more…)