I typically do "question driven development"[0] combined with Socratic questioning[1] for some of the deeper stuff. For example, with question driven developme

I typically do "question driven development"[0] combined with Socratic questioning[1] for some of the deeper stuff. For example, with question driven development in this context it was related to learning how to build a web application in a new programming language or web framework in an efficient way. But I think the same thing can be applied for a lot of things. It boils down to breaking things down and solving each sub-problem as it comes up linearly and then you bust out Socratic questioning to really explore a specific sub-problem to understand it better. So for learning a new language one of the first questions you might ask is "how do I install xyz language", which you tackle on the spot. Then you move onto the next question which might be "how do I install xyz web framework", and then you move to the next thing. Before you know it, you're a few hours into learning and you already solved basic things like how to get things installed, have a project generated, maybe respond with HTML on a couple of URL endpoints. Not only have you solved these problems but you have something to show for it too. Independent of question driven development, Socratic questioning has been one of the most valuable things I learned in the last couple of years. You can think of almost anything, big or small and attack the problem with the same set of questions. It almost works like magic when you combine both for learning and applying something where you're trying to reach an end goal. [0]: https://nickjanetakis.com/blog/learning-a-new-web-framework-with-question-driven-development https://nickjanetakis.com/blog/learning-a-new-web-framework-... [1]: https://nickjanetakis.com/blog/would-socrates-use-docker-today https://nickjanetakis.com/blog/would-socrates-use-docker-tod...