My guess: You're focussing too much on a top-down learning strategy, but have reached a point where you should take some time and switch to more of a bottom-up aproach at least for a while.
More like figuring out the details before trying to build stuff; knowing how the language runs and how certain syntax features translate to behavior depending on their input. This is what ultimately gives one the ability to reason about code without having to run it, which is essential both for debugging and preventing bugs before they even happen.
My guess: You're focussing too much on a top-down learning strategy, but have reached a point where you should take some time and switch to more of a bottom-up aproach at least for a while.
I guess the bottom-up approach you refer to is to start building more things?
More like figuring out the details before trying to build stuff; knowing how the language runs and how certain syntax features translate to behavior depending on their input. This is what ultimately gives one the ability to reason about code without having to run it, which is essential both for debugging and preventing bugs before they even happen.
Thanks for your advice, appreciated.