The problem in that advice is the "just". Weather is coding or e.g. wood working if you want to learn it you need to do it and just reading up on a ton of theo

The problem in that advice is the "just". Weather is coding or e.g. wood working if you want to learn it you need to do it and just reading up on a ton of theory and advice without doing it is very inefficient as you won't be able to really internalize the advice without some practice related to it. So what you normally do: - you read up a bit on the most fundamental basics, this might be a very small bit like safety advice for wood working or the general idea what a program is - you concurrently start trying it out ("experiments"), start learning more about it and _reflect_ on your experience and results in context of what you learn - you repeat with increasingly more in depth topic - at some point you move from learning with doing experiments not used anywhere, to improving while practically applying your skills on non experiments. You still might sometimes need do experiments through to evaluated if some new understandings you have are right And this can also be used for electronics, e.g. you read about e.g. resisters in a row vs. parallel and then you try it out in an experiment. E.g. with this kind of boards where you can just stick in parts this is pretty easy to do. Anyway here is the 3 rules: 1. Learning without practical application is inefficient hard and likely to go somewhat wrong. 2. Blindly trying without reflection of why things turned out the way they did tent to yield increasingly less improvements and then stagnate. 3. Learning all by yourself without reading up on things and getting other peoples opinions and feedback is making your improvements way slower then they could be.