Reception for developers to overcome procrastination

There are programmers who "live" their work. They think about work day and night, they are not distracted by petty domestic problems (they are above it, they “hover” over it). But this situation is not all programmers. Many people need to be successful in work, at home, at the stadium, and at the climbing gym ... You probably understand. However, such multitasking leads to the fact that you need to return to the tasks at work. And then there is a psychological resistance that leads to procrastination. To solve the problem of procrastination of the beginning of the working day (or even the beginning / continuation of work after the break), this method is proposed.

Before you begin, take a sheet, tablet or other means where you can record your thoughts. And start to write down your thoughts about the current project / task:

1. think about what to do? - list the functionality that you want to implement (maybe only today), list what requirements you need to implement, what goals the development should achieve;
2. think about how you will implement this , which classes, functions, methods you use, which algorithms are best to use;
3. think over, allow yourself to consider the implementation in detail , compare algorithms, compare possible approaches, think about the names of functions, possibly variables, think over API, details of the user interface, if your task includes developing a UI;
4. think about what functionality is best implemented first , think about why it is worth doing;
5. think about how you will implement this functionality .

If you can begin to implement, then proceed.

If you're still reading ...

You can also, before you finish work (go home from work) briefly write about what you can do next time (next business day). And when you come, start by reading these notes. And then proceed to the reception to overcome procrastination.
')
Successes! And successful work.

If you are still reading II ... (or why it works)

If you read articles on procrastination, you will learn that:

* Procrastination occurs when there is uncertainty in the success of the work

Using this technique, you can consider the task and, if you wish, answer questions regarding the best implementation of the task. You are not in a hurry to do coding and come across a wall of a hasty and impossible decision. You have a stock in the form of what you have thought of solving the problem. All your experience allows you to use the advantages of many years of development in order to evaluate the problem on the paper, the problem you have already solved, and use this experience to figure out how to solve another problem.

* After, relatively speaking, climbing or karting evenings, you just may not want to do the work

This technique makes it possible to start with the easy part of the task. At an easy pace. (Most likely, you write more slowly than you think.) If you are a genius of 10-finger dialing, then you can just slow down when using the technique. A letter gives you the opportunity to better reflect what you have written - you can re-read, and evaluate and think over again what you have already written. This can serve as a trigger for further thoughts.

Also you are using the reception, already working. Yes, you do not encode. But you are already working on the code. If a lot is done “in mind”, why not code it?

* Procrastination occurs if there is a fear of failure.

OK. But what is more likely you will fail: hastily written code - or thoughtful code? Where will be more errors?

If you are still reading ... (or do you still have questions ...)

Procrastination is a rather complex problem. Only one trick is offered. If you want to learn more, then I suggest an article on additional techniques for winning procrastination: How I struggle with procrastination - and usually win .