I know these principles:
Define the constrains and operations,eg constrains are the rules that you cant pass and what you want determined by the end goal,
operations are actions you can do, "choices" .
Buy some time by solving easy and solvable piece.
Halving the difficulty by dividing the project into small goals and blocks.
The more blocks you create the more hinges you have.
Analogies which means : using other code blocks, yours or from other programmers .
which has problem similar to the current problem.
Experiments not guessing by writing "predicted end" code, in other word creating a hypothesis, about what will happen if you do this or that.
Use your tools first, don't begin with a unknown code first.
By making small goals you ll not get frustrated.
Start from smallest problem.
Are there other principles?
