One of the most annoying things about being a programmer is when you’re trying to figure out how to implement a feature and then suddenly someone interrupts you.

Interrupt 5 minutes, lose 1 hour.

Programmers who want to increase their productivity need to learn how to manage their time.

If you have the same desire, learn the following time management techniques.

Turn passivity into initiative

Programmers learn to proactively manage their time and have a plan in place before things come to them. Such as:

(1) Meeting

Attend selectively. Attend only necessary meetings and eliminate unnecessary ones.

For meetings that must be attended, it is necessary to know the content of the discussion before the meeting and form your own opinion as far as possible before the meeting.

Limit the amount of time you spend in the meeting — you get your ideas expressed, others heard, and results.

(2) Communication

Programmers give themselves a daily schedule of when to do development and when to do chores. This way, when a colleague comes to you for advice or a discussion, you can make it clear that you are busy coding and debugging, and make an appointment to come back to you at your own free time.

Use the four quadrant method to arrange work items

Covey, an American management scientist, proposed a time management theory, which divides work into four “quadrants” : urgent and important, important but not urgent, urgent but not important, and not urgent and not important.

For important and urgent matters, deal with them as soon as possible.

For important but not urgent matters, deal with them immediately after dealing with important and urgent matters. Take care to avoid them becoming important and urgent.

For urgent but not important things, first of all to find a way to turn them into not important and not urgent things, if you can not change, find a way to find someone to share.

Don’t do things that aren’t important or urgent!

Learn to say no

Programmers say no to extraneous items and unreasonable demands based on their current state of work and the urgency of the task they are undertaking.

Think twice before you act

After receiving a task, programmers should first think clearly about the working ideas, possible risks and solutions, and then start to do it. Don’t get a request and start writing code without thinking it through and thinking it through as you go. This may be fine for simple requirements, but for complex requirements it will take more time.

That is:

Improve the efficiency of time management, proactive management of the first mountain

Think twice and say no. Time management quadrants

Bibliography: Three Courses for programmers: Technical Advancement, Architecture Cultivation and Management Exploration, author: Yu Junze et al., publishing house: Publishing House of Electronics Industry

About the author: Wang Xiaoshuang, who has been engaged in the promotion, implementation, evaluation and improvement of GJB5000 for a long time, is now committed to the research work of GJB5000 consultation, software process improvement and software engineering capability improvement.

Well, that’s all for today’s article. Thank you for reading it. If you like, give it a triple link

As a programming learner, if you want to improve your programming ability, learn C/C++ programming knowledge and data structure, and strive to become a high-paying algorithm/software development engineer in the future!

C language C++ programming learning exchange circle, QQ group [464501141] wechat public number: C language programming learning base

Share (source code, project actual combat video, project notes, basic introduction tutorial)

Welcome to change careers and learn programming partners, use more information to learn and grow faster than their own thinking oh!

Programming learning books:

Programming learning video: