Well I think that planning should be a very large percentage of the total time on the project. I mean planning in detail to the point where the coding is just filling in procedures you've already planned and testing them. It may not seem as much fun this way, due to not feeling like you are on an adventure and anything can happen, but it's more professional for sure. It also means that if 80% into the plan you realise you need to rethink some earlier stuff, you don't have to recode it, or worse, bodge it.
I used to not plan as a hobbyist and it's fun, but nothing got finished. A plan is also a motivational tool as you can see what to to next and cross off stuff you've already done.
I used to not plan as a hobbyist and it's fun, but nothing got finished. A plan is also a motivational tool as you can see what to to next and cross off stuff you've already done.