In test-driven development, we aim to follow the red, green, refactor cycle. That is: write a failing test (red), make it pass (green), then make it good (refactor). In A Refactoring Workout: Relentlessly Green, Katrina Owen describes two rules for refactoring under green:
That means that "the size of a step is limited by what your editor can revert with a single undo."
I'd like to talk about a few patterns of Vim usage that let you do more with each change. Some of these techniques use core functionality, while others will use plugins such as surround, UltiSnips, and exchange. I'd like to finish with a discussion, inviting the audience to suggest more tips and plugins in a similar vein.
The voice of @vimcasts and founder of @fromPeerToPeer. Author of https://pragprog.com/book/dnvim2/practical-vim-second-edition bio from Twitter
Sign in to add slides, notes or videos to this session