Ten lines of code in three weeks is generally not acceptable, of course. It happens when someone gets a job that is not appropriate for his or her skills. With your level of interest and achievement in your work, you will likely be recognized as an expert in your field in five or ten years. Then you will have an even harder question, "How do I cash in?"

At this point in your career you are noticing that you may become a top contributor. I sense that you may be wondering, "I've been working with a poor performer who has a bunch of experience. How will I differentiate myself from people like this? Who will get the bigger raise? What if I'm on a project, and I'm counting on someone like this for a critical component? Will we just fail or will I have to just do all the work?"

Management books are about this sort of thing. You might want to read a few. The Mythical Man Month is a good place to start.

It is quite a thrill to learn a whole new big technical topic like unix and perl, as you mentioned. I recommend that you supplement your technical learning in two ways:

First, choose a technical area that interests, you, and keep up with it. Pursue this technology for your personal enjoyment. Choose a new technology to study whenever it pleases you. This is rewarding in so many ways!

Second, read a few management books. Read the ones the managers in your area are reading, even if the books or the managers are insipid. There are many books about management, but most have only enough content for a magazine article. If you want more information density, read the magazine "Harvard Business Review." It is expensive, so you might want to just read it while 'shopping' and sipping caffeinated beverages in your local big-chain bookstore.

/msg me if you want fewer or more OT management/office politics discussion.
It should work perfectly the first time! - toma