The Pragmatic Programmer #4 : Be the Worst or be a part of more competent team

This is a very subjective advice and specific case may vary based on your own career ambitions and area of expertise, I can point to most of my team members and figure out few attributes in which they are better then me, however this advice is the most impactful of the lot and can be heard in it's various incarnation, this is a modification of The Apprentice Pattern book1 and essentially asks you to distribute your masters, if you are part of a group which is qualitatively better then you than you would pick up patterns from them all the time.

As an example, at the start of my career, one of my coworker was into all sorts of hack-ish script which he wrote from time to time to fix small issues here and there and enhance his workflow, I hadn't written a single useful bash script until that point but seeing him automate a seemingly tedious task by spending 15 minutes of it gave a motivation along the way, I now write simple scripts from time to time to automate the boring tasks that come my way which in turn enhances my overall throughput.

This example might look like a one off thing with minimal utility but these things add up, a simple script I wrote to find all the JIRA IDs committed across releases took me less than 15 minutes and uses around 6 different bash commands, doing this manually takes about 45 minutes working through JIRA and is essentially an error-prone task depending upon level of engagement.

I used to be amazed by my manager's ability of keeping things in his head while working on a release but when a part of that responsibility fell under me, I went to him for advise and what I learned is he has devised several mental models and workflows to manage all the information in bunch of text files and timers, I might have been able to figure it out over a course of year or two by myself but having learning from somebody's experience is a lot faster and doesn't wastes anybody else's time(this else can refer to your company too) along the way.

I would say this is one of the most useful advise that is there in the book, alternatively, this sounds true to the core if you thing about the whole process.

Links