Ben McCormick, a web developer, writes about JavaScript, Vim, Backbone, Jest, and developer tooling.
HN links it for JavaScript and Vim tutorials and his Jest snapshot testing review, which a Facebook engineer recommended; one commenter found his Vim series shallow.
Your articles are entitled "Learning Vim" so one could expect a little bit more depth and actual "teaching". And not promoting crap like Janus… installing that shit is the opposite of learning. It's like paying someone to do your homework for you.
http://benmccormick.org/2014/07/07/learning-vim-in-2014-working-with-files/
was ridiculous.
In "Buffer Management", you don't talk about :find or command-line completion or the wildmenu or the possibility to use mappings or the fact that one can use buffer names to navigate or tag-based navigation. And under "Plugins", the following sentence (and the mandatory list of plugins) is not really helping you to get your point across:
The good news is that Vim has solutions. They're just not baked into the Vim core.
Seriously, don't do that under a "learning vim" umbrella. That series should be called "Get Vim to look like all those screenshots without worrying about learning to use it".
Hi! I work on JavaScript Tools at FB.
There is a fantastic post by Ben McCormick about the up and downsides of this system: http://benmccormick.org/2016/09/19/testing-with-jest-snapshots-first-impressions/
Snapshots aren't the only feature of Jest; it is simply one assertion in our assertion library. There is a ton of other stuff in the framework that makes setting up a test environment and writing tests easier.
My philosophy for building a test framework is to build a good feature set to help you out in any situation but the user should be in total control. This allows you to find the best way to test your code which I've found to be extremely subjective. The choice of test framework and test methodology seems almost religious at times and I've deliberately tried to stay away from these conversations.
If you find yourself annoyed by some aspects of Underscore, you might want to check out Lodash[1]. Lodash's API is a superset of Underscore, though you can create custom builds with only the parts you need. In general, Lodash performs better and has fewer bugs than Underscore. Unlike Underscore, Lodash has 100% test coverage. Also, Lodash has some handy things like _.cloneDeep(), and semantic versioning. That means your package.json can have "lodash": "3.x" in its dependencies without worrying about breakage.
For a more in-depth discussion of the differences between Lodash and Underscore, I recommend Ben McCormick's Underscore vs Lo-Dash[2].
1. https://lodash.com/
2. http://benmccormick.org/2014/11/12/underscore-vs-lodash/
"Vim as a Language"[0] is a similar article I benefited greatly from back in the day.
One additional tip once you start using things like d8k: Try "set relativenumber" in your vimrc. It makes all except the current line display offsets rather than absolute line numbers.
Initially, this seems silly, but you quickly realize that if you're at line 1668 and need to delete up to line 1619, it's much more helpful to see line 1619 listed as "line 49" rather than "1619" and having to do the mental math to figure out that the command you're looking for is "d49k".
[0] https://benmccormick.org/2014/07/02/062700.html
Thanks for the book I'll take a look on it, it seems interesting.
For vimtutor it's introduced in the first part http://benmccormick.org/2014/06/30/learning-vim-in-2014-the-basics/
The most disturbing thing when learning vim is the fact that shortcuts actually "means" something rather than being near your fingers. Like the old flashioned way to use shortcuts in RTS games vs grid modes.
Several made this point, that Backbone is stable, not abandoned. I agree! I said so in the post. My concern is with the libraries around it. I've elaborated in this followup post: http://benmccormick.org/2016/03/09/stability-vs-decline/