CodeNewbie Community

Cover image for When Should You Start To Write A (Technical) Blog?
Ayu Adiati
Ayu Adiati

Posted on • Updated on • Originally published at adiati.com

When Should You Start To Write A (Technical) Blog?

... Do you find that writing about your learning like this helps to cement the knowledge?



Hello Fellow Codenewbies ๐Ÿ‘‹

I received that comment when I shared my blog posts on Twitter a few days back.
And that's what inspires me to write this article.

A Little Something About Me

I am a conservative person. Let's say that physically writing on paper with a pen gives me great satisfaction.
And I always take notes whenever I learn something.
I just love writing.
About anything,
that interests me.
Writing gives me joy!

The Reason

The initial reason, the reason that gets me down to this web development journey, was I wanted to create and style my own website. A place where I could write and share the ideas in my mind and share my photography hobby.

Along my learning journey, I've read plenty of technical writings and motivational posts. Honestly, they often tickle me to transfer my notes and share my journey in public.
But impostor syndrome did a great job in holding me back.
I'm not an English native speaker. Let alone in English, writing a technical article in my mother tongue is very challenging.

There are plenty of great posts out there talking about the same topic that I want to write. Would people even read mine? What would they think about my post? What if it doesn't interest anybody else but me?

Will people understand my English? And if so, can they receive the message that I want to deliver clearly? Would it help them in some way as those posts that have helped me, that have motivated me?

Those thoughts linger in my mind for almost the whole period of my journey and that's the reason why I was holding myself back for so long.

Start To Write

One night my daughter had trouble sleeping. So I couldn't learn anything because she was waking up every half hour.
Instead, I wrote and published my first post: How I Got Into Learn To Code. And it felt good because I was finally able to beat the impostor syndrome and did one of the things that I originally wanted to do (even though not on my own website yet)!
I wrote a couple more articles on a little more technical topics afterward.

National Novel Writing Month (NaNoWriMo)

I was then drawn back to the learning process and didn't have time at all to write in public until my beloved community Virtual Coffee threw the initiative to do NaNoWriMo as this month challenge, where we try to accomplish 50,000 words as a group.

For me personally, it is one way to get back to writing again and beat the impostor syndrome that sneaked back in.
I finally found back my initial reason to learn to code, and it motivates me, even more, to go further in my journey.

Does Writing About Our Learning Help To Cement The Knowledge?

In my opinion, what I find most crucial in cementing our knowledge is by practicing what we learn.

Create a simple mini project after we learn about a topic. If you don't have any idea on what to build, don't get discouraged.
Redo what you just learned and see if you can replicate and understand the syntaxes and the whole flow.

Then write the process down, document everything. From the trouble you face, the parts that make you pull your hair, the steps that you need to take, new information that you gain, everything.

For me personally, writing things down on a piece of paper with a pen helps me more to retain knowledge.
Whenever I encounter something and get lost but I've written it down before, I somehow have a familiar feeling towards the topic or the problem.
And most of the time, that would be the time I would get back to open my notes and found out that I've encountered it before, and mostly along with the steps that I took to achieve the result.

So YES, in a way, writing helps to cement our knowledge.

Writing is also a medium to share our knowledge, to help some fellows out there who go through the trouble that we went through, even to help our future self because we have documentations to go back to whenever we get lost.

Writing is not your thing because you prefer to share your knowledge verbally?
You can create video content or start a podcast to deliver your knowledge if that's more convenient for you.

Conclusion

  • Start to write now and don't wait!
    Don't let anything that worrying you holding you back from writing. No one creates something good for the first time. Just like any other skill, practice is also needed to be better in writing.
    Don't overthink how people would react to your post. Write for yourself and the future you first. The rest will follow.

  • Don't make it a big deal if you realize that you published a post that has mistakes or lacking some pieces of information in the content. You can always edit and update it later on and point out the updates. People make mistakes.

  • Documenting our knowledge not only cements what we've learned but also could help other people and our future self. And we won't even know that perhaps our journey could motivate someone else. Sharing is caring.

So what are you waiting for? Start it today, or even better... start it now! ๐Ÿ˜€

Discussion (8)

Collapse
sheriffderek profile image
sheriffderek

Start To Write

don't wait!

Create a simple mini project after we learn about a topic

Then write the process down, document everything. From the trouble you face, the parts that make you pull your hair, the steps that you need to take, new information that you gain, everything.

Write for yourself and the future you.

Totally agree with this. If you start now - you'll be a tech rockstar in 5 years. I'm a big fan of substack and getting a mailing list ASAP.

I'm concerned with how many people are "learning something" (just reading it) - and well... not really learning it - and then regurgitating it. Like "Today I learned: Just so you know - HTML and CSS aren't programing languages." Which isn't good for anyone involved.

Collapse
adiatiayu profile image
Ayu Adiati Author

True, it's sad.
I mean, for example, if you think about accessibility first when you create HTML, you'll stand out.
So I don't understand why they think that way, like this or that is not a programming language, this language is better than that one, etc. ๐Ÿคทโ€โ™€๏ธ

Collapse
mel_reams profile image
Mel Reams

There are plenty of great posts out there talking about the same topic that I want to write

I worry about that too and I keep reminding myself that I never look at just one single blog post when I'm trying to figure something out, I look at a few of them and see what they agree on.

Collapse
adiatiayu profile image
Ayu Adiati Author

Speaking from my own experience, don't worry about it too much ๐Ÿ˜€
You never know if someone prefers your article and benefits from it more than others.
Just start to write, at least for yourself first. For your own public notes ๐Ÿ˜‰
I'm looking forward to read your posts! ๐Ÿ˜€

Collapse
gauravrandheer profile image
Gaurav

Awesome !! just so you know you have motivated me to write technical content.

Collapse
adiatiayu profile image
Ayu Adiati Author

I'm happy to hear this, Gaurav!
Thank you ๐Ÿ˜ƒ
Would love to read your first post! ๐Ÿ˜Š

Collapse
adiatiayu profile image
Ayu Adiati Author

๐Ÿ˜Š