VimTricks: The Vim Newsletter
More than 2 years ago, Andy and I started a tiny little website called VimTricks on a whim. It was a place to showcase tidbits and tricks we had learned over our many years of using the Vim text editor. This month, we evolved VimTricks into something brand new: a vim newsletter. VimTricks is now a vim email newsletter that delivers new tips twice a week.
We have both been using the Vim for many years. We build all of products and services, like StatusGator, using Vim. For us, Vim represents the most powerful text editing tool available: customizable, extensible, and open source. But Vim can be daunting to learn as a beginner. Even advanced users have much to learn from the large ecosystem of plugins and customizations available.
Internalizing all the capabilities of Vim is a difficult process but one of the most effective ways we have found to do so is to write them down. In fact, the minute we launched VimTricks, we both realized how much more learning and exploring we were doing. VimTricks gave us a reason to find a better way to do things with Vim. Instead of using the same old roundabout way to make an edit, we would research and find a better way. Then, we’d write up a post, reinforcing what we learned. Just this process of discovery, writing, and editing, has proven to be an incredibly powerful way for us to improve our Vim skills.
And now, we are even more motivated to keep learning Vim because we hold ourselves to a deadline. Our Vim newsletter sends emails twice per week, every Monday and Thursday at 8 AM Eastern time. The feedback has been great so far and we are thrilled to keep learning and keep publishing.
The reception has been so great that we are proud to announce that after soft launching last week, we already have over 1,000 subscribers to VimTricks. If you want to join our Vim newsletter, register today!
VimTricks, the Vim newsletter, publishes every Monday and Thursday at 8 AM Eastern.
We are sorry that this post was not useful for you!
Let us improve this post!
Tell us how we can improve this post?