Comments on: 5 Good Habits That Will Make You a Better Coder

By: Ryan Miller

Ryan Miller — Tue, 04 Oct 2011 17:10:49 +0000

I think the concept behind #2 is solid, but perhaps the implementation should be different. I agree that if you can not explain in WORDS what you are trying to accomplish in code, how do you expect to code for it. So being able to describe and explain what you want to do is important, and doing so in comments is an option, I would rather recommend using test-driven development (TDD) as it forces you to think through the problem you are solving as well as test for it as you go.

By: David Litvak

David Litvak — Tue, 27 Sep 2011 11:55:44 +0000

Nice post… though… the comments stuff… is way wrong from an agile point of view… every agile developing method is against comments in code… as code should express itself…
A good technique for avoiding unnecesary comments is good object modeling (which is really possible in Javascript) and good naming conventions

By: shireesha

shireesha — Sun, 24 Jul 2011 11:30:07 +0000

thank you…..for great tips

By: Wonde

Wonde — Fri, 03 Jun 2011 07:42:22 +0000

Thanks a lot, great tips

By: Youpele

Youpele — Fri, 10 Sep 2010 21:57:08 +0000

This post has helped me stay some what focused as I’m teaching myself HTML(Late starter I know CS5 out already!). It takes a keen eye yo to study the code of javascript and css with HTML code.(hope I’m making sense:. I’m teaching myself as feel enthused by the prospect of being a home starter.

Great Post

By: Ron

Ron — Wed, 28 Jul 2010 19:37:05 +0000

Great tips, with one exception: Number 2:
I agree, that it might be helpful, to use some kind of pseudo-code or natural language to lay out a function at design time, but as soon as i write code, there are no comments anymore!
If you have to say something in your function, express it through code, by using meaningful variable names or good names for (sub)procedures/functions.
This is the only way to get sustainable readable and understandable code. The code is the documentation, no need for code comments.
According to tip 4 (read books), i can only suggest reading “Clean code” by Robert C. Martin.

(Sorry, i am not a Web Developer, but a Java Developer, so my attitude may be a bit biased…)

By: Bishal Pantha

Bishal Pantha — Sun, 25 Jul 2010 22:17:08 +0000

Great post to get Web-Tech enlightenment …thanks a ton Matt…

By: mark

mark — Fri, 16 Jul 2010 07:32:06 +0000

2. Write Your Logic through Comments
You have to be kidding.
Stop writing articles just to for the sake of writing an article.

By: Anees

Anees — Thu, 15 Jul 2010 07:20:57 +0000

Great article, Thanks buddy!

By: BrightLoudNoise

BrightLoudNoise — Wed, 14 Jul 2010 17:50:14 +0000

Good tips, although I suspect you meant tenets as opposed to tenants.