Going from one end to another

I’m good at starting something from scratch. Define the concept, make a detailed execution plan, create tons of tasks and make an estimate how long it will take to make all that happen.

I’m also efficient and systematic of completing the pre-defined tasks one-by-one. Just type on the code, test & fix and finish with a commit. And of course check how much time it took.

But then comes the part when the application and functionality is pretty much there and kind of already works if you are careful enough. The most interesting tasks are done but there’s still lots to do to achieve the finish line.

Then the problems arise. I start making excuses, dropping features and lowering the bar. “Do I really really have to waste my time with the rest of the tasks? I’m sure there’s something more important to do out there, in some other project maybe…”
That’s also the point when you have to face your bad architectural and design decisions from the beginning of the project. Accept that you weren’t as good as you thought…

I have to learn to keep on working until I can say that this is complete and I can’t come up with any flaws that I knew how to fix.

Not just prototype but make production quality applications!

 

Leave a comment