|
|
|
|
|
by JohnnyFlash
5192 days ago
|
|
One of my new years resolution's was to become a finisher. Last year I started a number of projects, I wrote a lot of code. I learned a lot. Nothing saw the light of day. This year had to be different. I needed something to show for my time. I became a finisher. To make this change I did 3 things: 1) Reduce the scope on any new product ideas. Simple is best. I will only allow myself a month to work on something. If I am working longer than that and have nothing I can publicly show then the scope has probably buried me and nothing will ever be released. 2) Say Fk it and quietly release the project. Quietly because it isn't 100% finished. There are little problems here and there. I would like to spend weeks tweaking a feature but if I do it without releasing anything I will get bored and start a new idea. Once released I can iterate, improve and add functionality. 3) Tell everyone what I working on as I am doing it. This means I need something to show at the end of it or I will look silly. I then tell people in order of technical expertise about its release. Tech savvy people understand the concept of a beta and even an alpha. Others... not so much. So far its working. I have already released something this year. Its still a bit iffy but it is improving each week. I am becoming a finisher. |
|