10. Requests that begin with, "All you have to do is...".
9. Deadlines fabricated by others.
8. Single character variable names.
7. Being spoonfed requirements on a need-to-know basis.
6. SQL Selects within iterations.
5. Requests that describe how, but not what.
4. Variable names that don't describe what they are.
3. Meetings without beer.
2. Dropping everything for the emergency du jour.
1. Top 10 Lists that infer that all programmers think alike.for (int i=0; i<items.length; i++) { //do something small with items[i] }
However, I should confess that I usually write it as ii:
for (int ii = 0; ii < items.length; ii++) ...I personally find the doubling awkward, and with modern editors I use semantic searching much more than raw text scans so the benefit of doubling is marginal, but there is at least one sensible reason you might choose to do it.
As I said before, it's probably not as useful with modern IDEs that have semantic search capabilities, but there is a genuine reason some people prefer the "ii" style.
(I'm not a huge fan of point-free, I'm just being facetious ;)