alt Hacker NewsWhat is the goal?
That needs to start all conversations in this area. Not everyone had the same goals.
Second, what is your specific problems?
Again not everyone had the same problems. There are common problems with common solutions (often multiple conflicting solutions that work in isolation but perhaps not for your life), learning what works for others can thus be helpful. Beware, not all problems are big enough to be worth addressing for you.
The important part is find what works for you. Sometimes you don't need to measure what you learned - which seems to be your concern- if it is important and you learned it you will remember when needed. Of not you need to look it up again. It can be liberating to realize that you don't need to measure everything. Sometimes that isn't good enough though, so back to the first two questions.
> That needs to start all conversations in this area. Not everyone had the same goals.
That's a very good question. In my case, when learning in the mode I described above, my brain is often more worried about the amount of unknown stuff versus focusing on what I am working on at the moment. With that, learning starts to feel like a burden and leads to burnout (even though I enjoy solving problems). I can become closed off to new information, and disheartened at everything I don't know.
The problem I'd like to solve is being able to retain excitement about learning while working on projects without it feeling like an obligation. There are probably more base issues to address for this (eg. being less controlling of outcomes). And there's particularly a lot of doubt now that AI coding is the norm, and I feel uncomfortable with moving faster because I feel attached to all the details. That has turned the debate much larger about what anyone really needs to know if they can blitz through stuff at the speed of prompting.