I'd have to go with dws on this one. I've only been coding in Perl for a little while now, but almost any computer trade has a similar effect.

For example, I used to work doing computer support (network maintenance and user training mostly) and it's really nice at first because people like it when you come by and fix the problems they're having and help them with their troubles. You get to know a lot of people and they all get to know you - definately a good thing. Unfortunately, this can sometimes become a bit of a drag.

Often, I'd go on a work order to take care of a rather simple problem and I'd find myself gone for hours because someone would spot "The computer guy" and they'd have something they'd like help with.

Granted, I find this to be a small price to pay - if I didn't, I wouldn't stay in computers. Frankly, I think it's worth the trouble of helping people to work with computers. Whether you're programming or wiring a network, if you do a good job and you're nice to the people around you - they're bound to like you - just remember, most of them can't do what you're doing for them. In that, it's important to help them learn to do what you're doing for them and to get them to not be afraid to try to do what you do. If you can teach them to perform some of the simpler tasks on their own (even if they'll never actually learn to code Perl as well as you), you can spend your time working on much more interesting projects.

- Sherlock