How to start a project and not stall in a rut?

The first step is the most difficult. To continue, it gets easier because the first experience suggests further steps. But how to start? Sometimes comes up with the idea for a service or tool and, after scribbling on a napkin or whiteboard, I want to implement the idea in code. But immediately POPs up thousands of routine things: to configure workspace, design DB schema, to tie the authorization and authentication, and so on. All these little things out all the original fuse and coding the most interesting you can just hold out. How do you deal with that?
March 19th 20 at 09:23
7 answers
March 19th 20 at 09:25
A good incentive to work is when you approach the fridge and it's empty.

Usually the routine is 90% of the work.
We must learn to live with it.

You can become epogam when he will be able to decide what you want to do, and taking only the "delicious" challenge. But in this case the routine will remain, perhaps it will be less.
Deferred compensation works poorly in such situations - dorthy_Boyle commented on March 19th 20 at 09:28
@dorthy_Boyle, Yes, this is an extreme case, but there is an incentive not to bring this up in the future :-) - Alycia.Ondric commented on March 19th 20 at 09:31
March 19th 20 at 09:27
This is the effect of the desire for immediate gratification. Inherent in spoiled children. You need to realize and get used to the fact that life is rarely "fun and interesting", and usually consists of routine. Those who may not realize, end up either homeless or drug addicts.
March 19th 20 at 09:29
March 19th 20 at 09:31
Take your finished template project (framework) where all already have a login, dB, server, and so on.
If no suitable - spend a couple of days and do it once.

But to be honest - it seems that you just much you want to fantasize about how cool you're implementing the idea than the work you already do, no changes are necessary, you already get your dose of dopamine in the optimal way.
Continue to draw on napkins and have fun :)
March 19th 20 at 09:33
If these little things stop you, and you should not start any projects. In any project there is a routine and it is necessary to do or find someone who will do it for you.
March 19th 20 at 09:35
Not design in the beginning! Immediately drank the functionality, the most basic and complex. This will make it clear whether will you cope with the conceived in General, check the idea on the viability and feasibility of the test load that will give you an idea of the required hardware.

And if everything is OK you will get great satisfaction and new power to all this wrap in the normal architecture and to present it all together.
March 19th 20 at 09:37
All depends on the situation. If you procrastination is one thing, but if analysis paralysis is another.

Find more questions by tags Designing softwareProject management