Photo by Glenn Carstens-Peters on Unsplash

🗒️ I've been thinking a lot about start writing. There are many positive reasons to do this:

  • 📚 Challenge and share knowledge

    • This is like trying to explain things to others, but I also feel that it's like explaining things to myself. Writing what you think you know is a good way to analyze deeply your knowledge about a particular topic and it forces you to reason and go beyond your limits.

  • 🤗 Opportunity to help others

    • The first reason could be only for yourself. You just need to open a note-taking app and start writing. But all the research and reasoning you do for yourself could also be useful for others. If you publish your thoughts, there is a chance you make someone smile.

  • 🤓 Research new topics

    • If you like writing, you need to find some topics. Having a blog might be useful to push yourself and read seriously about something you always wanted to know about.

  • 😎 Build a personal brand

    • This could be seen as a selfish reason to write, but, if you take your work seriously, people might notice it and your word could be spread.

  • 💬 Improve communication!

    • Soft skills are way too valuable. This one in particular! Improving your writing skills is a nice side effect and it will be helpful for you and your work.

The thing is ... it could be scary. Maybe it's just the impostor syndrome writing here but it was somewhat difficult to me. I've been reading a lot of blogs, articles and newsletters for a long time now and I felt that I wanted to do it. I wanted to be part of this writers community, but I struggled with commonalities such as What do I want to say? Do I have proper knowledge? What if I write something wrong? What if people don't like my topics? and several other what if's...

Overall, I think it's a mix of impostor syndrome 🕵, simple procrastination 🛌 and time management ⌚.

🕵 About the first one, I keep telling myself it's bullshit, specially after I developed a lot of self-awareness in my job as I grew (and still growing) as a Tech Lead. What if I write something wrong? Nothing! Hopefully someone will point that out and tell me (politely, right?💓) that I was wrong. I'm also winning by making a mistake. Everyone is learning everyday. Curiously (or not), I find this extremely related to make your code/side-projects public.

🛌 The second one is almost as difficult as the first one. I've been kind of a procrastinator my whole life (having a to-do degree thesis for 4 years, and counting, is the best proof of that), but sometimes I was able to overcame it by ... starting! I just needed to start! That was the one and only thing I really needed. A simple and beautiful start. Once I did that, I entered into some sort of flow state and I was able to end the task, like I'm doing with this post. Just take the first step.

⌚ The third one is, I think, the easiest to beat. Pick a couple of hours a week ("macro" time-management) and implement some ("micro") time-management technique (Pomodoro is the most mentioned overall). Without a doubt, some posts might take more than a couple of hours, but this set a rhythm. Just, don't forget to start!

🏁 I set myself a goal: Write a blog post every 3 weeks. It's not that much (I guess...) and it will challenge my consistency and procrastination. I'm currently listing topics on what to write. There will be a mix of development, tools, leadership, conferences, books thoughts and recommendations and, of course, personal experiences. I should say that most of it I will be re-publishing to dev.to community (If you are a tech person and don't know it, you definitively should!). I joined the community a couple years ago as a reader and I really like the people and the environment.

So, a new journey begins. Let's see what happens...