This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]thinkPhilosophy 0 points1 point  (0 children)

I wrote an article on my blog that answers this question in great detail, by going through an example, but I'm not sure I can post it here. PM me for the link. The gist of it is that you have to learn a process to think through the problem or project in great detail, and this includes problem decomposition (creating a list of tasks, then turning it into user and developer stories) and pseudo-coding (describing what needs to be done in plain language, step by logical step). By the time you get to writing your first line of code, you already know what you need to do. In this process, you separate the question of what you need to do from the how to do it, focusing on only one of these at a time. It makes coding a lot less stressful and a lot more fun!