Here is a neat problem solving workflow i borrowed here.
It is really helpful when you're in the middle of a sprint and you've hit a
blocker.
Another strategy which i would advocate for and which normally works is
describing the problem to a colleague, most of the time you will answer yourself
while in the process of explaining the problem.
Heavy reliance on google isn't good as many have pointed that out.Try to solve it yourself if you really want to sharpen your skills.
Also i would also recommend taking a nap.Research shows that it leads to higher levels of productivity especially during the late hours of the day, you can find a good guide on taking a nap here.
1) Try it.
2) Get up and walk away.
3) Try again.
4) Go for a walk / do some pushups (gets the blood flowing)
4) Try again.
5) Read the documentation.
6) Try again.
7) Go to the whiteboard and draw it out.
8) Keep trying.
9) Go back to the docs.
10) Try again
11) Look through some sample source code.
12) Try again.
13) Meditate.
14) Try again
15) Keep trying
16) Google it
17) Find a good answer on stack overflow.
It is really helpful when you're in the middle of a sprint and you've hit a
blocker.
Another strategy which i would advocate for and which normally works is
describing the problem to a colleague, most of the time you will answer yourself
while in the process of explaining the problem.
Heavy reliance on google isn't good as many have pointed that out.Try to solve it yourself if you really want to sharpen your skills.
Also i would also recommend taking a nap.Research shows that it leads to higher levels of productivity especially during the late hours of the day, you can find a good guide on taking a nap here.
1) Try it.
2) Get up and walk away.
3) Try again.
4) Go for a walk / do some pushups (gets the blood flowing)
4) Try again.
5) Read the documentation.
6) Try again.
7) Go to the whiteboard and draw it out.
8) Keep trying.
9) Go back to the docs.
10) Try again
11) Look through some sample source code.
12) Try again.
13) Meditate.
14) Try again
15) Keep trying
16) Google it
17) Find a good answer on stack overflow.