This article is the fifth of the series aimed to teach Vim from the ground up:

Can you picture an adventurer, going deeper and deeper into a mysterious cave, knowing what’s waiting for her (mostly rocks and bats) but at the same time wishing to be surprised by some rare gems and abandoned treasures?

This article is part of a series about Zsh:

“The completion offered by Zsh is great, but could it be better? Why not trying to understand how it works? I could then configure it for my own needs!”

What are the oldest and most complex tools we use every day, source of the biggest challenges we have to face in our daily work?

Our brain and our natural language.

We all had the pleasure to implement the wrong features, bring complex solutions, and create bugs because of miscommunication. Communication will always be flawed because it’s imperfect. But we can’t really “be” in the mind of the other, so it’s the best tool we have to collaborate. In that regard, active listening can help us get better.

This is the fourth part of this series to learn Vim from the ground up:

Dave, your colleague developer, just read Vim for Advanced Users before going to bed. He wonders what’s next: Vim for Unstoppable Creators? Vim for Godlike Developers? On these reassuring thoughts, he falls into a deep sleep.

“You used inheritance in your code! Are you crazy? It’s forbidden! It’s clearly written in the Laws and Mantras of Good Software Practice Everyone Must Follow™ hanged in the toilets!”

Your thoughts about the nice Youtube video full of cute dogs you saw yesterday stop abruptly. Anxious, you look on your right: Dave, your colleague developer, is yelling at Davina, your desk neighbor. All three of you are working for the fantastic company MegaCorpMoneyMaker, the famous e-commerce which can sell ice to penguins.