The fastest coding is no coding. Some pre-programming thoughts: Problems are easier to fix the earlier you find them. Try to define the problem (get it clear i

The fastest coding is no coding. Some pre-programming thoughts: Problems are easier to fix the earlier you find them. Try to define the problem (get it clear in your head); try to define the solution. A minimal product can help (does it solve the problem? is it the problem real?), or mocking up a pretend solution (e.g. a manual backend, or no backend), even on paper, or with a tool like balsamiq. Can you solve the problem using an existing tool, perhaps by modifying the problem to fit (constraining it, generalizing it, or transforming it)? This can be embarassingly effective, esp if you have NIH syndrome and just want to code. Can you make the cause of the problem go away? ie Doctor, my arm hurts when I do this. Don't do that. Estimate times, by sub-dividing the tasks, then doubling the estimates. Then re-ask what is really essential. It can change the balance of what alternatives are reasonable to consider. [x2 seems to account for one's optimism. But confirm it for yourself: make some estimates and check what happened.] Reread The Mythical-Man Month. eg He suggests 1/6 of project time be allocated to coding. (p.20, anniversary edition); the rest is planning (1/3) and testing (1/2)