Blog by Daniel Hauck. Sysadmin, Developer, Blogger.

… for writing.

HAHA! Click bait.

Now I got your attention or at least you are still on my site. Continue reading, I don’t want to steal much of your time.

Haven’t you

had a few articles about vim for writing? Yes, I have. And I’ll leave them here for ‘historical’ purpose. I’ve written a lot in Vim. I’ve written almost 50 – 60 % of my book about tmux in Vim. And I still have the opinion, Vim is worlds best and most advanced text editor.

And here comes the evil

Editor, the word EDITOR. You can edit texts in vim so efficiently, that it can be toxic. I am using it for 6 – 7 years now. About 5 of them I’d consider myself as a power user. I spent a lot of time, training myself to use Vim. Remember shortcuts, commands, crazy stuff, tinkering with my .vimrc and so on. I do not regret one second of this, because Vim will probably be one of my favourite tools for the rest of my life.

But when it comes to writing, this kind of efficiency, like I mentioned above, can be toxic. Writing is a creative process. And at the time of writing a chapter or a paragraph, you shouldn’t care about typos, missing articles and so on. You can fix that later. Your writing program or auto correction will yell at you early enough (BTW: turn them off or ignore them while typing). Because I am so familiar with Vim, I always jumped back when I saw an error or something and totally lost the flow and blocked creativity.

To cut a long story

If you are writing an article, not a tutorial about programming or so, break out of your comfort zone (what a stupid word) and use another tool. Efficiency can be distracting in some ways. And I learned, when it comes to writing, less is more. Less features, less stuff to think about.



There are no comments.

Leave a Reply