March 2001
Intermediate to advanced
288 pages
4h 56m
English
Other people are going to look at your code—they may find bugs—and they are very likely to comment on its readability and maintainability. If you picked a consistent style (see Perl of Wisdom #6) and consistently commented your code, they should have fewer nits to pick in that department.
You are not bound to accept every comment from the people reviewing your code (people who should be your peers; this process is not a management function), only the ones that make sense. The more you can keep your ego in check, the better, because you want to be able to learn from the process; merely showing off how brilliant your code is won't do anything to improve your craft.
A mammoth bone of contention that often arises is the issue ...