To blog or not to blog

It is obviously very easy not to write a blog; for me, it works out of the box. So why should I change something and start writing one?

Well, possibly I will not, and this will stay the only entry here—let’s see. It is not that I am one of those developers who hate to write, in general or documentation in particular. The opposite is true; sometimes I like and even enjoy writing, and I do it even in my spare time. Sometimes even with visible results.

So I know that writing takes time, and writing in a foreign language—English, in my case—takes even more time. And there is writing and writing. Taking notes and typing something quickly into the editor for yourself is one thing. Bringing it into a form so that others can read it and have a clue what the text is about is another thing. In short, writing a blog would take some of my spare time that I would otherwise use for my other hobby projects. And this is the only con I can think of.

So let’s focus on the pro side. There are a lot of reasons to spend more time writing. The primary reason for me might be becoming a bit more skilled and faster through more regular practice in writing and structured thinking. And you can’t go wrong if you follow the words of a person like Leslie Lamport.

So it is to blog, and let’s see how much of my spare time I can redirect into training my writing skills.