Productive development or how to write code without affecting the brain and nerves

Updated: 11.01.2013
Productive development or how to write code without affecting the brain and nerves

Many developers, and not only that, faced with stressful situations at work and side effects, such as constant irritability, etc., after working hours. Next I will try to formulate the basic criteria for productive development without compromising their own health and common sense.

(By the example of Dynamics 365)

First, you need to realize for yourself that nothing is impossible, every problem is solved, but any problems - a price, be it resources, time, or something else, but not as the health and sanity. Terms do not allow you to relax and to allocate between 15 and 30 minutes to the "Coffee?" - It's too bad, because the brain is multi-ton locomotive flies to the desired path, and if time does not slow down, you can smudge it on a rock which is itself. Paradox? The human brain is generally in itself a paradox. What I mean is that, for the development of productive, you need to be distracted from the work. If you suddenly feel that you have something does not work, you need to escape - drink coffee, smoke (no matter what he wrote on cigarette packs MOH), take a walk, etc. Need to do it to your "steam" is not knocked down himself. When you are distracted, the brain does not turn off, just keep coasting run at a moderate speed, but without the irritating factor in the source code before the eyes or "not converging cents" while continuing to deal with the most "impossible" task.

Second, it is not necessary to spend some free time, for a period of testing your design or something like that, to perform a new task, you can not at the same time keep in mind the nuances of both tasks. The only exception is for a long time of testing (validation) of the 8-hour and up. Even if you know that the testing will last more than 8 hours, do not immediately start to the new, give "locomotive" of the previous problem to drive off at a decent distance.

Third, work on inspiration when it came - do not follow the first two points. Paradox? I already wrote about above. The most productive work done on inspiration, here in this moment not be distracted by external stimuli - mail, ICQ, phones, bosses, customers, and others like them. If distracted, you could lose a lot more time to be included in the design, if not distracted and brought development to its logical end.

Fourth, do not know where to start? Start with the first paragraph of your job, just start out the task on the items described by the customer or by someone else, something else. You'll see that slowly your "steam" starts to accelerate.

Fifth, try not to take work home, serfdom abolished as early as 1861, if management does not believe it, it is their personal problem, your good sense of priority. Except as described in the third paragraph.

Now you think I'm advocating inaction in the workplace? It is not, while "distraction" should not exceed 15% of the total working time. Jobs involving all hands only exist in the mind mediocre leaders, but the fact that they are not recoverable resources, the human brain, they do not understand and do not want to understand, that's why they have and there are "jobs involving all hands" because "Resources" are working at full stretch.

The result of following these few criteria at the approach to the development, and any kind of creative work, is that you'll be happy to go to work, therefore, more productive. You cease all madden because jobs involving all hands will cease to exist for you.

Author: Oleg Maistrenko, Dynamics 365 Developer


Other blog posts

We apply OKR methodology in Neti since 2014. We started from a quarterly planning, but then understood that no ambitious goals can be achieved per quarter. So we switched to semi-annual intervals....
As you know, Microsoft recently has launched Dynamics 365 Business Central. And we are proud to announce we have launched intracompany training for sales and development departments:Why do we need it...

Subscribe for blog updates

Get updated with our blog new articles via your email!

Subscribe now