Comments on: Why I don’t write code comments

By: Louco por automatização! « Pedro Augusto Freitas de Souza

Louco por automatização! « Pedro Augusto Freitas de Souza — Sat, 03 Apr 2010 03:53:03 +0000

[...] “Radical” e “extremo” são palavras que têm uma conotação muito negativa, mas ser radical ou extremo pode ser muito útil quando se tem um propósito como esse (ou então para se fazer uma abordagem como a que eu postei sobre porque eu não gosto de escrever comentários no código). [...]

By: Guilherme Chapiewski

Guilherme Chapiewski — Fri, 04 Dec 2009 07:45:35 +0000

@Anderson

Sorry, it’s not implemented. But the good thing is that it is Open Source, you can do it if youwant to! I’ll be happy to integrate your patch into the project

By: Anderson

Anderson — Tue, 24 Nov 2009 13:46:07 +0000

How can I use the “no-reply”?

I’ve expected a “.replyTo(…)” !

By: Louco por automatização! | Planeta Globo.com

Louco por automatização! | Planeta Globo.com — Wed, 15 Apr 2009 22:12:49 +0000

By: Louco por automatização! | Guilherme Chapiewski

Louco por automatização! | Guilherme Chapiewski — Wed, 15 Apr 2009 06:13:22 +0000

By: Lucas Oleiro

Lucas Oleiro — Wed, 08 Apr 2009 14:34:53 +0000

To support your post, there’s a good book about the same subject with a lot of other arguments:

http://www.infoq.com/articles/clean-code-book-review

By: Carlos

Carlos — Wed, 08 Apr 2009 12:46:46 +0000

I agree 100%! Quality should be a concern since the first moment…

but I think lack of expressivity (or expressiveness?) in code does not necessarily make it crappy code.

By: Guilherme Chapiewski

Guilherme Chapiewski — Tue, 07 Apr 2009 22:18:30 +0000

@Carlos

This is a common misconception about Agile.

Although you must build features and functionalities iteratively and incrementally, the QUALITY have to be built in since the very first moment!

You will not write crappy code to be rewritten from time to time, you will write high quality code that will be refactored every time. You have to write high quality and well tested code so you can quickly refactor your software to accommodate changes – that’s Agile.

I insist that comments can and should be avoided, but, as any other Agile rule, this is not a silver bullet.

By: Carlos

Carlos — Tue, 07 Apr 2009 18:20:45 +0000

It seems you are suggesting that expressivity in code must be delivered since the first attempt. I beg to disagree, obviously it depends on the length of iterations because expressivity means rewriting the same code several times, but generally in agile projects refactoring is an iterative and incremental activity.

Comments can be useful to handle this transient situation if, as any other tool, used correctly.

By: Rafael Naufal

Rafael Naufal — Tue, 07 Apr 2009 16:49:48 +0000

I think this problem arises when people don’t know how to factor concerns (which are not coupled together) in objects collaborating to realize some purpose.

So, this kind of code ends up being messy, rot and very difficult to maintain.

A good design approach talks about objects with one responsability and clear method names indicating their purpose, with indirections isolating things that change freqüently from things that stay the same.