Learn in Public
swyx.io
swyx.io
And share their findings.
Moreover, it's good to be exposed to scenarios where the code is technically correct, but the attitude of the author ought to raise red flags - for example, unnecessarily representing a solution as authoritative, discounting other approaches for dumbass reasons (such as preferring fewer lines for its own sake), saying that a problem is "simple" to solve, you "just" have to do this, etc. They tend to have the effect of shutting down critical inquiry, and that's a good thing to learn how to recognize.
In other words, you can learn a lot from hamfisted tutorials and toxic teachers.
Learn and get paid for it asap. Learn what your client/project/employee needs and everything around it - this is the fastest and most rewarding way.
What definition are you referring to, because that statement doesn't make sense.
However, there are several studies[1] that show dramatic improvements in retention and understanding from material vs. just studying it. So if you consider retention and understanding to be the goal outcomes of learning, forcing yourself to structure your thoughts about the material enough to communicate it with others has clear benefits to learning rate.
[1] Example: https://www.sciencedirect.com/science/article/abs/pii/S03614...
I believe in writing a technical blog when you're starting out because it can help you help a job early on in your career. A message to a Linux User Group got me an interview and my skills got me the job.
Does anyone do livestream development? How has it been?