How not to knock a developer out of the “stream” state

/ photo by Rachel Johnson CC

Developer time is an invaluable resource that is constantly lacking. We at IT-GRAD take this issue very carefully.
')
Professionals who know how to “tame” time, negotiate with him, know this as well. The secret of their success lies in the fact that they are trying to extract the maximum from each “working” minute, so they are not very fond of their terms of a “deal” with a time continuum being violated.

In this regard, we would like to give some tips for company managers and project managers, which will allow you to work and interact with the development team as efficiently as possible.

“Do not starve” developer ideas ...

Ideas like little scary kittens. If you scare them, they will stop coming.

Therefore, any new idea requires evaluation - no need to hurry.

If a bright thought that has visited your head does not directly relate to the task to be solved by the programmer, then report it, but do not demand a momentary answer. A good developer will write down the thought and come back to it later.

This is necessary in order not to knock a person out of the “stream”, since it takes about 15 minutes to return to the state of concentration.

Lucy Jo Palladino in his book “Maximum Concentration” tells Lucy Jo Palladino about the issues of maintaining concentration and working mood in a fairly accessible way.

... and do not overload your "ideas"

Careful attitude to ideas is great, but you do not need to load the developer with an endless stream of new ideas. Try to put your thoughts on paper, and then cross out the excess from there - thoughtfully determine the essence.

You will be surprised how much it will improve the quality of communication.

Also it is worth thinking about what exactly you will say to the developers. Most recently on Habré discussed this topic.

Do not turn the work into a puzzle of 32 256 elements

We need to find something in between short-term ideas and "multi-ton" projects.

Break the tasks into small pieces and distribute them so as to squeeze the most out of a particular situation. The main thing is not to make people “jump” from one task to another - they “drop out” from the state of concentration.

Concentrate on creating the conditions for self-improvement. The professional growth of a specialist will only positively affect his success: he will learn new skills, learn new technologies more deeply, and begin to offer creative solutions.

Build their work according to rule 80/15/5 . 80% of the time the developer will spend on their core work. To devote 15% of the time to more complex tasks, and the remaining 5% of the time to satisfy one’s own curiosity.

This approach will create the conditions for working on interesting tasks.

No need to chase the result

It sounds really strange, but in this rush lies the reason for the many failures at the finish line. The time it takes to bring the code in a neat look is really worth it.

Refactoring and additional efforts to optimize the UI are necessary so that all the magnificence of the functions does not turn into one big mess.

It may be interesting: the literature on creating interfaces on the Stack Exchange.

Not all “dance in a waltz tempo”

People work in a different rhythm. Each programmer chooses a moment to work on these or other tasks in order not to waste extra energy and avoid confusion.

It should be borne in mind that people have recessions of activity, when any work will be ineffective. Be patient, they are necessarily replaced by periods of decisive action.

Sometimes it is worth taking time to think about the situation so that the developer can understand in which direction he should move in order to avoid an impasse. The main secret to saving time is to do everything efficiently and the first time.

PS Several materials on the topic of time management and projects.

What else do we write in the blog " IT-GRAD ":

Source: https://habr.com/ru/post/304658/

All Articles