I have skimmed this book, written by Alan Vermeulen, Scott Ambler and a few other people. It contains programming guidelines for Java programming, and it is just so sloppy, or outright meaningless. Here's a bunch of examples from that book:
3. Do it right the first time.
Uh? Oh, now I know exactly what to do!
5. Indent nested code.
Wow! That is revolutionary!
9. Use meaningful names.
Oh, my, I was thinking of using meaningless names!
29. Qualify field variables with "this" to distinguish
them from local variables.
To this I say: Get an IDE instead. They do it for free.
33. Keep comments and code in synch.
Why would anyone NOT do that?
46. Establish and use a fixed ordering for Javadoc tags.
Now, they're really concentrating on important stuff...
61. Avoid the use of end-line comments.
62. Explain local variable declarations with an end-
line comment.
Now, where were the reviewers of this book?
68. Build concrete types from native types and other
concrete types.
Sounds really recursive to me. Nasty nasty.
93. Use threads only where appropriate.
Thanks! Very helpful.
94. Avoid synchronization.
Bummer. It looked quite useful to me.
100. Use lazy initialization.
Oh, really. Always?
102. Reinitialize and reuse objects to avoid new object
construction.
103. Leave optimization for last.
Previous Topic
