- Contact the Key reviewer in advance and confirm when they are available
- Having all codes packaged in a zip file and check into server and send out the link.
- For changing existing code, print out the diff version in pdf ….
- make use of computer when doing a code review
- clarify and confirm
- write clear meeting notes and send out the meeting notes afterwards to confirm the changes.
- if necessary, let’s have another meeting.
- Ask him /her to revise the bad code of the guy after one hour’s long talk. This is to test:
- good working attitude
- willing do stuff even feel tired
- have good sense of taking pressure
- refractor ability that we strongly need
General Management Sense
- Demonstrate that you ARE ABLE TO work well with your peer managers.
- When questions comes, try to get them solved with a reasonable way.
- Don’t quarrel which doesn’t solve any problems and will lead you to a worse situation.
- Being a manager, you have the right to decide the next step as you are the one who take responsibility.
- Listening to others’ advice doesn’t mean you have to take’ em. Take only if they are right.
Team Management:
- Think as a Team.Then make decision on key stuff. Leave things to others to decide.
Trust Relationship Build Up
- Know what the most important stuff to the individual
- Over sharing sometimes
Manage Up!
- Know what the are good at and leverage it.
- push to meet with you even they don’t want to. ‘cos they are nice so they don’t want to feel bad if they don’t meet with you.