I was blogging a lot in the past for different topics: books, music, parenting and when I was younger, generic rants about the world.

But I never dared to blog about programming.

Actually, I tried once more than 10 years ago, but after choosing the name and the layout on WordPress I never wrote an article... I really did not feel like I was good enough to give anyone advice.

My perception was that if you are going to write about something - then you must know the shit! you must be the super expert on the topic, donating your immense knowledge to the ignorant masses...

Therefore I quit immediately.

Then I read about GaryVee's theory "Document - don't Create" by GaryVee and found, right here on Dev.To, this post: 5 reasons you should write that blog post
Even though over these years I definitely increased my experience and skills I still don't think I am an expert but I was convinced that

I should document my learnings and at the same time share my tricks and tips.

The fact that I had my Trello board full of new years-resolutions about sharing knowledge ( with public speaking, opensource and writing) gave me the jump start to open the blog on 28th of January.

So far I managed to write at least 1 post a week. My plan is to stick to this - not more not less than 1 post a week. Be it some kind of "philosophical" post about programming and career or some quick tip of code refactoring, I saw that writing a post take quite some time and I always feel I should do something more productive.

What i really like of blogging is, especially for more technical posts ( still too few) I noticed that organizing the post allows me to try out different options, reorganize my thoughts and definitely consolidate my knowledge.

What I found sometimes discouraging is seeing that after some hours spent writing a post, you receive just a handful of views.

How do you organize your writing? How long do you take to write your avarage post?
How do you deal with the frustration if your post does not have the deserved success? ;-)