>Doing something quick and dirty for a first draft and improve it later on often leads to better results in the long run than planing and over-engineering a sol

>Doing something quick and dirty for a first draft and improve it later on often leads to better results in the long run than planing and over-engineering a solution beforehand, because you can start refining details much earlier or throw away bad approaches without investing too much time. If it's something not too big, sure. Won't work so well if you don't know what to even do because you don't have any idea what the structure of the program's going to be like. I've found planning much more beneficial for myself.