View profile

On Writing About What You've Learned

On Writing About What You've Learned
By Mastering JS Weekly • Issue #77 • View online
People often ask us why we’re working on Mastering JS. After all, blogging is a terrible way to make money. And tech is a notoriously tough niche because of tech-savvy competition and rapidly changing topics.
There’s a litany of reasons why we’re continuing to work on Mastering JS. A major reason, though, is to write down what we’re learning while doing our day-to-day work. Like our friend Shawn Wang’s “Learn in Public” initiative. But we’re less concerned about the “public” part and more about the “learn” part.

Clarify Your Thinking
Writing is a great way to learn. Not only do you get a handy guide you can refer back to when you need to brush up, the exercise of writing something down helps solidify your understanding. Like taking notes in class.
Writing helps you understand what you did to solve a particular problem. When you’re focused on finding the solution, it is easy for the individual steps to blur together. Writing helps make the individual steps more explicit in your mind.
Writing down your solution can also help you identify potential pitfalls and tradeoffs. When writing tutorials, I often find myself considering alternative solutions, and sometimes the alternative solution is better than what I originally came up with. Either way, considering the alternatives is enlightening.
For example, writing about how to convert a date to YYYYMMDD format in vanilla JavaScript lead us to considering the tradeoffs between several different alternatives. Along the way, we learned a lot about locales and timezones, and got a solid review of date methods. And we discussed how much code can sacrifice terseness for readability, or vice versa.
Make Wi-Fi Money and Teach Others How
Mastering JS is a small, but noteworthy part of our business model. We don’t expect to become a unicorn via ads and affiliate marketing. But we believe there are major benefits to writing down what we’ve learned, and we might as well pick up some extra revenue from it. Better to write on our own blog than let all the revenue go to Medium.
Never get paid for the same work only once
Never get paid for the same work only once
Here’s the idea: if you complete a task, you get paid for it and move on to the next one. If you complete a task and write down what you learned on a public blog, you at least get some residual page views that you can monetize. Any individual post will likely not make much, but, like in Calculus, the sum of a lot of small actions can add up to something meaningful.
As a side effect, building a popular blog can help you come up with additional revenue streams: contract blogging, SEO consulting, etc. Sometimes, you don’t need to do extra work, you just need to leverage your existing work.
Most Recent Tutorials
Array toString() in JavaScript - Mastering JS
Format a JavaScript Date to YYYY MM DD - Mastering JS
What Does `app.use(express.json())` Do in Express? - Mastering JS
What We're Reading
Inversion of Execution | Temporal Documentation
Did you enjoy this issue?
Mastering JS Weekly

Pragmatic web development. No bloatware allowed!

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue