Learning in public can't be the fastest way to learn by definition. It takes time to write and publish. It takes A LOT of time to write <i>well</i>.<p>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.
Further reading on a related notion: Bloom‘s (revised) taxonomy. The idea that mastering a skill means producing new content related to that skill, which is considered the highest order skill. Lower order skills would be „understanding“ and „applying“ (using).<p><a href="https://en.m.wikipedia.org/wiki/Bloom's_taxonomy" rel="nofollow">https://en.m.wikipedia.org/wiki/Bloom's_taxonomy</a>
This is from the same guy who I believe said "systems > goals" (or least repeated it), forgetting the fact you need goals to accomplish before you can build systems to accomplish them.<p>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.
I work on a lot of opensource side projects that may be of interest to some and thought it might make sense to livestream it. I can usually set out to do a specific new thing and close it out in one session so might fit the format.<p>Does anyone do livestream development? How has it been?