A couple of other points I'd like to suggest
- A lot of people in this business jealously hoard information to themselves, apparently thinking that if someone else learns what they've learned their job will be threatened. Obviously this doesn't apply to perl monks, or they wouldn't be here! The opposite is true - sharing what you know is the only way to enhance your reputation. Don't worry about losing your advantage, just make sure you're constantly learning.
- Following on from that, its always worth learning something new. A different programming language, a different methodology, project management skills, a different programming area (database, network, web etc etc etc).
- Learn to make realistic estimates of the time needed to do a piece of work, even if you're currently in a job where you don't need to, and always factor in some contingency time.
- Following on from that, make the distinction to yourself and others between elapsed time and effort time. If you say a piece of work will take 3 days, you'll be expected to finish by thursday. If you say a script will take 3 days effort you won't be made to look stupid by unresolved dependencies like, for example, access to a particular machine, completion of a spec etc.
- Both documentation and commenting are important. One is not a substitute for the other. Getting a good reputation depends at least as much on other people being able to read and maintain your code as writing clever, fast, bug free solutions, if not more
VGhpcyBtZXNzYWdlIGludGVudGlvbmFsbHkgcG9pbnRsZXNz