How do you balance the creep function with time constraints?

Question

I like programming as a rule. Difficult material is easy to make as quickly and correctly as possible, so that I can go through it and not see it again.

But most of my coding is fun, and when I get into the “zone” I just like it.

This is where I make a mistake by spending too much time, maybe adding features, maybe writing it in a cool or elegant way, or just making neat prototypes.

• How do you know that this happens before it exceeds your time interval?
• What do you do before you run a potentially fun piece of code or while you return it?
• When is it okay to allow yourself to "rage" and just enjoy it without worrying about the consequences?

-Adam

Answer 1

Save the detailed priority list / error list. review it often, then balance the fun work with the bugs / functions you need to perform.

Answer 2

Give yourself a hard time - even for your own projects. Otherwise, you will just save the settings and add functions ad infinitum.

Answer 3

( ). , SQL- .:)

. , , . , - , , -, .

Answer 4

. , , , , .

Answer 5

"" , , .

, , ;)