Be careful what you are good at
Michael Feathers wrote about his shift in focus from people to programming, which got me to thinking. To me, the two pivotal points of Michael’s post were:
- He feels himself pulling away from a deeper involvement in teams and organizational change
- Be careful what you’re good at
Being the self-centered guy that I am, I immediately wondered how I might fit into Michael’s post. I feel similar to Michael about pulling away from a deeper involvement in teams and organizational change. One of the reasons I felt compelled to start Obtiva’s Studio was because I had grown more interested in developing software than consulting. Coming from my previous career as a family therapist, I suppose I shouldn’t be surprised by my tendency to move from people into programming: I was drawn from a people-centered career into one that involves a balance of technical mastery and teamwork.
Michael’s post sort of implies that there are only 2 activites for him to choose from: 1) agile transitions, and 2) legacy code improvements. I think I know what he’s saying when he advises us to “be careful what you are good at.” Michael is probably better than most everyone on our planet at these 2 complex endeavors, but it sounds like he’s reached a point where they have become less interesting. Maybe I’m wrong about that? Michael can correct me. :)
But he makes a super-important point: be careful what you are good at. I have found myself purposely holding myself back in certain situations because I didn’t want to distinguish myself at something that I didn’t enjoy. I feel strange about that, but I feel like it has helped me grow into a role where I am best suited. Now, imagine writing a book about legacy code but not enjoying improving legacy code. Or writing a book about apprenticeship but not enjoying apprenticing people. Can it actually be dangerous to blindly do your best with every opportunity that comes your way? Do you risk finding yourself promoted into a role that you’d rather not be in? For instance, should you write a book just because a publisher has agreed to publish it?
I think one of the critical tasks to maximize your career is to know yourself. It sounds like for Michael, he has recognized that learning and sharing the deep, fundamentals of programming are what makes him tick. I have recognized that working closely with startup founders and delivering rapidly for them energizes me like few other activities. What makes you tick? Are you carefully becoming good at that activity?
