I'm putting down Python books. I've absorbed so much language, syntax, and library/framework info over the last six months or so, however; I face what V. Anton Spraul calls the "blank screen problem". As I develop to solve problems which project ideas address, the drag on progress is more than I'd realistically like to see apart of the process. I need to become a better problem solver before I can become a better programmer.
Taking inspiration from George Polya's How To Solve it and Spraul's How To Think Like a Programmer, I've created a process to help solve problems. When it takes more than five minutes to carry on I...
- Is there a good case for code re-use?
Should I still be stuck with the problem, at this point I...
- reduce the problem and focus on finding progress for just one constraint
- hit the interpreter and sandbox with ideas
Take frequent breaks; water, stretch, etc. There's a discussion thread on the great, online developer community, Dev.to() which I started. Share your process! Myself, and I'm sure others, would love to see how you tackle problems.
Problem solving is a creative endeavour, the mind best solves problems when relaxed.