I am quite happy that I was able to find the causes of two very difficult and intriguing problems at site today. These problems involved other systems whose teams were unable to support us on-site. With systems of systems, there are complex dependencies. Our trusty servlet, which always work, had failed.
I had to put on my "Debugging Cap", look beyond my system (beyond our codes and log files), and even look into the codes of others (with their permission of course). Such instincts paid off! It is crucial to have knowledge of systems connectivity and their processes workflows. So is the mastery of own system's mechanisms and architecture, in order to connect the dots. It is also important to not completely rely on others, although your system depends on other systems. Thus, the self-satisfaction was enormous.
I told my dear wife about it and she made a very enlightening comment. She said that my role now should not be solving difficult problems, but to be able to pass my skills to my team mates and teach them what to do in such circumstances.
I told my dear friend about it and she made a very remarkable comment. She said that I shouldn't expect everyone to do what I do as they ain't me. Instead I should focus on documentations and transferring of knowledge among the team whenever we have time.
And I think to myself... the lesson from this incident is that it is important to be proactive (the First Habit of Highly Effective People). Only with that attitude, you'll be able to solve difficult problems. However, it is no big achievement to be able to do everything yourself because we will never have the energy to go on forever like that. Instead, only the wise ones will be able to pass on the relevant knowledge and skills, and delegate the tasks for better efficiency. I guess I am still very much a worker and not yet a good leader. Much much more to learn...
I had to put on my "Debugging Cap", look beyond my system (beyond our codes and log files), and even look into the codes of others (with their permission of course). Such instincts paid off! It is crucial to have knowledge of systems connectivity and their processes workflows. So is the mastery of own system's mechanisms and architecture, in order to connect the dots. It is also important to not completely rely on others, although your system depends on other systems. Thus, the self-satisfaction was enormous.
I told my dear wife about it and she made a very enlightening comment. She said that my role now should not be solving difficult problems, but to be able to pass my skills to my team mates and teach them what to do in such circumstances.
I told my dear friend about it and she made a very remarkable comment. She said that I shouldn't expect everyone to do what I do as they ain't me. Instead I should focus on documentations and transferring of knowledge among the team whenever we have time.
And I think to myself... the lesson from this incident is that it is important to be proactive (the First Habit of Highly Effective People). Only with that attitude, you'll be able to solve difficult problems. However, it is no big achievement to be able to do everything yourself because we will never have the energy to go on forever like that. Instead, only the wise ones will be able to pass on the relevant knowledge and skills, and delegate the tasks for better efficiency. I guess I am still very much a worker and not yet a good leader. Much much more to learn...
Comments