Pet Peeves Version 2.0

[filburt1]

My VB pet peeves:

1. Using SendKeys. Usually there is a better way.
2. Using OLE. It just slows down your app and makes it chunky.
3. Calling everything Form1, CommonDialog1, Winsock1, Text1, etc. Get a clue!
4. Using deprecated methods. If global is deprecated, don't use it. If an API call is deprecated, don't use it.
5. For all languages: not using consistant naming conventions. Constants should be in ALL_CAPS_WITH_UNDERSCORES_AS_DELIMITERS for every language (or at least C, C++, Java, Basic, QBasic, Visual C++, and Visual Basic.)
6. No comments. At all.
7. Using an excessive amount of color in a program. Not only does it look amateur, but color-blind people might miss the point.
8. Speeling wrng n a proggie. It makes you look stupid. (But I probably spelled something wrong in here )
9. Not bothering to look in the help or (with VB5 but not 6, I think) the Books Online. Asking how to use a command on the forum is stupid if the syntax and examples are right there in the help.
10. Using variants. At all. They are slow, can cause conversion (is it a string or a number?) problems, and are native to Visual Basic.
11. Not completely testing your program before releasing it into the public. As the programmer, you know how to use your own proggie. The user may not.
12. Similarly, no documentation. Microsoft is famous for it. You don't have to be.
13. Not using control arrays. txtEntry1, txtEntry2, txtEntry3, and code for each one could be replaced with For i = 0 to txtEntry.Count - 1 and then the code.
14. No encapsulation. Don't chuck all your code in one module! Networking code should go in one module, UI code should go in another, other code should go in another.
15. For all languages: Not using arrays, similar to 13. Instead of having Strings called Card1, Card2, Card3, just make a freaking array!

Any comments? Please vote in the poll!

Also post any feedback and your pet peeves!