Explore >> Select a destination
|
You are here 
|
brainlid.org | ||
| | | | |
blog.langworth.com
|
|
| | | | | What a response! The original "Vim After 11 Years" post was very popular, and it prompted a lot of good responses on Hacker News and Reddit which were peppered with useful tips and plugins I didn't know about. I compiled all of them along with some additional tips from friends and coworkers, then tried a lot of them out, and finally distilled it for you here. Enjoy! | |
| | | | |
www.adamalbrecht.com
|
|
| | | | | In order for testing to become part of your development workflow, it needs to become a habit. And like any habit, its biggest enemy is neglect. Too often I'll be in a rush and not add tests to my code for a day, and that turns into a week and then a month, and suddenly I have an app where half of my codebase is untested and the other half has breaking tests. There are many things you can do to help keep this habit (hooking up a CI server immediately comes to mind), but an important one is to make running your tests as quick and easy as possible. One way I do this is by making my ruby tests (either Rspec or Minitest) extremely easy to run while I'm using Vim (and Tmux). With one quick keystroke, I can run the current test file or individual test in a new Tmux pane. | |
| | | | |
markodenic.com
|
|
| | | | | Free programming books, algorithms, public APIs, and much more. | |
| | | | |
itwont.work
|
|
| | | in which I muse on my relationship with tech. (imported post) | ||
