I have another question.
How would you go about solving unsolved problems? It's quite to difficult to not end up in rabbit holes and lose track of what you are doing.
I have often ended up chasing the wrong thing/going in the wrong direction.
I have another question.
How would you go about solving unsolved problems? It's quite to difficult to not end up in rabbit holes and lose track of what you are doing.
I have often ended up chasing the wrong thing/going in the wrong direction.
This one is a little trickier for me, for some reason. Probably the first step is to identify the specific problem you need to solve. We need to find 'Q', or the relation between P and Q. Maybe you need to break the problem up into peices, and solve one at a time. How to build a website? How to build a UI? How to host?
Then identify and capture the facts as you know them. X -> Y, P, Q. This is a research phase where you want to understand all that you can, within reason. You don't need quantum mechanics for your average application design. So you need login for your site? Pictures? Forms? Charts?
Then conceive of a framework for analyzing. On a 2D plane, polar or Cartesian coordinates for instance, as well as picking the origin. Maybe you need logic, or something else. Richard Feyman invented his quantum Feyman diagrams to help him understand quantum mechanics. Calculus, derivatives, and integration were invented for calculating the areas of spaces between complex curves, and two people, Leibnitz and Newton, each came up with their own notation to represent the ideas of adding infinitely tiny slices. Sometimes you might need to create a tool. For webdev I think this is like, single page app or server side generation or whatever.
Once you have data, and a framework, you can analyze for a solution. I also think of something about graph searches might be applicable: breath first is best when the solution is close to the source, and depth first is better for farther answers/more exhaustive searches. Ok, server side generation has these options with these pros and cons, jsx, templating, whatever.
Also, one of the best strategies in programming (and life) is: "small steps, always," from the pragmatic programmer, which I highly recommend. Feymans book are also incredible, he teaches learning as much as physics.