I find this technique quite helpful when learning new concepts, modules or languages as it forces me to explain the material in my own words. This only improves my understanding of the subject, sort of like writing notes.
I love that -- my target audience is normally the "me" of a couple years ago. I think it makes your posts really real and helpful for people if you can really relate to the material.
The bonus of actually writing the post though is that often, the end product of the blog post is different to the solution you found!
For example, I started learning Electron. Read the docs, found few tutorials and I now have the end product. All I need is to copy paste the code in a blog post. However, whilst writing the text to tell the "audience" what the code does, I'm seeing refactoring opportunities all over the place. So for me it's all about placing a stamp of approval to my understanding. If I can blog about the code I found in stackoverflow say, then you can be sure by the time I pressed publish, that code is mine, in that I'm no longer the person that copy pasted the code with his fingers crossed. Because you now need to go and read the section of the docs which the stackoverflow user kindly linked to but you were to excited to bother reading :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is gooood!
I'm amazed by the detail in the boilerplates. I might do that one day.
At the moment, I'm at that phase where I'm just writing tutorials as I'm learning new things. So my target audience is me few weeks or few days a go.
(I find myself using the word "then" a lot. "first we do X, then Y, then Z.")
Also, a tip that might help someone:
When writing my posts, I use the speech feature on mac and listen as it reads my text.
I'm able to catch my spelling errors and also whether or not the text sounds how I intended.
It has helped me so much that I end up listening to my text few times before I'm satisfied that ... I can't do any better. :)
Oh that's an awesome idea! Thanks!
Hello, Ali !
Can you share this template in Sketch?
I find this technique quite helpful when learning new concepts, modules or languages as it forces me to explain the material in my own words. This only improves my understanding of the subject, sort of like writing notes.
I love that -- my target audience is normally the "me" of a couple years ago. I think it makes your posts really real and helpful for people if you can really relate to the material.
Ya, I've got a long trello card of Blog Post ideas that are all just "I should write about how to do the thing I just figured out how to do."
Maybe someone in my same position will Google the same problem and come find my solution, or not.
The bonus of actually writing the post though is that often, the end product of the blog post is different to the solution you found!
For example, I started learning Electron. Read the docs, found few tutorials and I now have the end product. All I need is to copy paste the code in a blog post. However, whilst writing the text to tell the "audience" what the code does, I'm seeing refactoring opportunities all over the place. So for me it's all about placing a stamp of approval to my understanding. If I can blog about the code I found in stackoverflow say, then you can be sure by the time I pressed publish, that code is mine, in that I'm no longer the person that copy pasted the code with his fingers crossed. Because you now need to go and read the section of the docs which the stackoverflow user kindly linked to but you were to excited to bother reading :)