You are a normal front-end developer, writing business code and working hard. The leader sees your good performance, has the heart to cultivate you, and gives you an important structure task, but you have already worked 9 to 9, now how to do?
Common Solutions
If you can’t finish working overtime, you should work more overtime until you finish. You should never betray the trust of the leader
- Brother I’m afraid you have life to do, not life to get results ah
- Overtime should only be used to solve urgent tasks, but overtime is not a silver bullet! If we change our closing time for the next month from 9 to 12 for this architecture task, it will definitely change from 12 to 2 in the morning because we added other tasks! There is no time to rest once you encounter online bugs or rush changes. Not to mention the damage to the body, the quality of both sides of the task will decline, there is no time to think, planning, review, it is easy to go wrong, give the leader
An impression of hard work but poor quality
Or,Don't coordinate resources and just do not complete the impression of unreliable
.
Prioritize, the urgency and importance of business and architectural tasks, and execute them in turn
- People who don’t pay attention to the leader’s tasks usually end up in a bad situation
- Generally speaking, the business is urgent and not necessarily important, but the architecture task is important but not urgent, so do the business first and then do the architecture! A few days later, the leader asked me how I was doing
The business is done this week and the architecture is done next week
. Let the leader be angry,I have the heart to cultivate you, but you perfunctory me!
Turn around the task to someone else, the next life to cultivate you.
Not really can not add to the work, leadership you find someone else to do it
- Reject the leader’s cultivation, miss the opportunity to give people a
An impression of being afraid of a challenge
- And while we’re talking about missed opportunities,
But at least his health was saved
“This may be a blessing in disguise.
Pull others to do together next first, or discuss with the leader to pull people to do together
- There is the suspicion of laziness and fear of challenge, and the achievement will be diluted, but it is a rare and feasible way
Pay attention to master the planning and assignment of the architecture task, grasp these to master the right to speak
Others are just workers, but no one is willing to do your workers!
Business and architecture work together, allocate time and develop synchronously, all slowly
Both sides think you're not paying attention
If you think you’re not doing well or slow because of another task, you’ll be treated more harshly!- At least don’t tell the business that you are developing at the same time, or you will die!
A better solution
- According to the
Complexity and time consuming
Split all the business and architectural tasks at hand- High complexity: third-party coordination, unstable demand, complex technology implementation, too many docking personnel, technology is too small or ahead of the audience
- Self coordination or upward
Coordinated development of resources
Hand over all of the low-complexity, time-consuming tasks (easy to hand off, manageable, with little achievement)
, depending on the situation, hand over the less complicated and time-consuming. Synchronize the task assignment profile to the leader- Before the critical time
Check Key Progress
To ensure that the schedule is controllable - Set aside your own time to work on complexity key task points
- All three parties are satisfied! Embodies the you
Have the courage to take on responsibilities, dare to challenge, high coordination ability, reliable work, strong working ability good impression
. Wait for a promotion and a raise
Aye aye aye, said about you, wake up, wiped saliva, the morning wake up to write the code! I looked at the few thin black hairs on the table. They were my lost youth…
Please like and comment