How is a test case supposed to explain why MAX_COUNTER is set to 5 or 20? Comments are the single-most important thing when writing code, in my opinion. When feature specs are lost, and documentation goes out of the date, you only have code. And if you're supposed to jump through hoops like test case code to try to divine WHY things are as they are, then you're dealing with really hard-to-maintain code.
I strongly suggest all developers to ignore this blog post, and to comment as best as you can.
> I strongly suggest all developers to ignore this blog post, and to comment as best as you can.
Bad or to many comments are better then no comments. Its not exactly hard to remove them, their absence will never break the build unlike not understanding the implementation!
Comments
What a terrible and self-righteous post.
How is a test case supposed to explain why MAX_COUNTER is set to 5 or 20? Comments are the single-most important thing when writing code, in my opinion. When feature specs are lost, and documentation goes out of the date, you only have code. And if you're supposed to jump through hoops like test case code to try to divine WHY things are as they are, then you're dealing with really hard-to-maintain code.
I strongly suggest all developers to ignore this blog post, and to comment as best as you can.
> I strongly suggest all developers to ignore this blog post, and to comment as best as you can.
Bad or to many comments are better then no comments. Its not exactly hard to remove them, their absence will never break the build unlike not understanding the implementation!
That's not exactly true, if the comments and the code have at some point diverged, the comments can only serve to confuse the reader.