Being a senior

Being a senior in a team does not just mean being productive, being a senior in a team means contributing ideas to improve the team, supporting the team when there is change, driving change when necessary for static means rotting, materializing the goal of the team.

Being a leader

I must remember if in the future I am a leader of some peoples, I must not immediately shun off my subordinates' suggestion, I must take time to think it through, instead of giving reply like "no it's not workable, it will involve a lot of unnecessary and unproductive discussion on this matter and still at the end nothing can be done", I must say instead "I know your pain going through approval process like this, I will talk to those peoples to revisit the process, no guarantee anything can be done, but I will try". Saying this I will reassure my subordinate that I care about their feeling, and I will always do something.

Professional

Condeming or complaining does not make me look professional, knowledgable or superior. It makes me an old grumpy bitch. However, if I state the problem and trying to find a solution for it, I am seen much more constructive.

Meeting and notes

I must remember to bring notebook to meeting or discussion, i will jot down when there are question or doubt, I must not interrupt the presenter halfway, I will ask question only when it is convenient.

One sentence reminder

When I remind someone for his mistake, I must remember that one sentence is enough, I must not further describe the detail of the event as it would make that person feeling embarassed more. The definition of mistake is, one knows what he supposed to do but accidentally misses some steps. Therefore, one sentence reminder is enough to bring that person back to track and would not embarasss him.

Social intelligence

I must remember intellectual intelligence maybe win me a degree certificate, but social intelligence is the one make me succeed in my career.

Code review

When we are practicing code review, and I know I am reviewing code of a senior developer, I must trust him and expect he should know what he is doing, I should pay attention to the overall design of the code, instead of individual line of code. I should not ask him to prove to me the code really works for I must trust him that he should already tested. I could ask him the reason of not writing unit test but i should not force him to do that because as a senior he should know what he should do right and I should respect his stance on it.