From a technical master to a technical manager , A common problem is not to let go ！ It's easy to understand , After all, other people are not good enough , Time and quality are definitely not as good as what we do , A lot of times I think ：“ I finished this job in half an hour , If it's up to you to do , It takes a week to finish , I've got to get in for an hour, tutoring and scrubbing , It's better to work hard for yourself .”
Little imagine , One thing for half an hour , One person for half an hour , It's a terrible time to add up . In the end, I was exhausted , The team didn't grow much , The output is not high yet .
The reason is , I'm afraid that others won't do it , Or it can't be done well .
To solve this dilemma , In fact, it's not hard to .
The first thing is to plan . Planning seems to have nothing to do with it , Why should I put it first ？
Because of technical management , The most important thing is to have a holistic view , Look at the whole team, the whole project , Instead of looking at a task, a person , When you're always staring at a small task , Naturally, I always want to do everything by myself .
Planning is forcing you to have a big picture , Look at the whole picture , Break down the task , Assign the task to everyone . When you look at the big picture , The tasks were assigned to the right people , Naturally, you won't always think about doing your own tasks .
In addition, planning must be in line with milestones , Otherwise, it is easy to make plans difficult to implement or deviate from the original direction .
Then there is the task of identifying important urgent and important non urgent tasks .
Why are you always busy ？ Because a lot of time is actually busy with some unimportant things , When you really have an urgent and important task to do , There is no time to take care of small things . If you're always busy with the little things you can't do , I'm very busy every day , But nothing , But it's delaying what's really important , As a result, the important and not urgent things rise to important and urgent things , It's been fighting the fire .
So we should distinguish the important urgent and the important non urgent tasks , Give priority to these things .
Something important and urgent , It's like an online failure , It doesn't matter if you do it yourself , Something important but not urgent , Stare at others and do , Make sure they do well . It's not important, it's not urgent , Let others do it , Just check it regularly .
The third point is to learn to decompose complex tasks into simple tasks .
A lot of times I don't do it for others , It's really because they can't do it , Do not know how to start . But if you can do architecture design well , Split complex tasks into simple ones , So ordinary programmers can do complex tasks together . And in the process , They can also get good exercise and growth .
The fourth point is to discuss more plans in advance , It's a logistics summary .
If you start a task, do it , That's not a good result , But if before you start , Let's talk about the plan first , And then based on the results of the discussion , Let the programmer write a simple design , Talk about it a few more times , Basically, everyone's thinking is the same as you , There will not be too much deviation in the implementation . You don't have to worry. They've grown up .
After the mission , I'll help you to make a double check , Analyze what's done well, what's right , What is not good enough to be improved next time . Several times down, everyone can grow up together .
Last , Let's talk about the picture @ Beauty, her father How to do it , He belongs to a high rank , Not only let the team do it , At the same time, give the team the right methods and tools to guide , most important of all , He's been motivating the initiative of the team , Make them feel like they have a sense of ownership , Make them feel like they're growing , It's amazing
The beauty of software engineering #