Explore >> Select a destination
|
You are here 
|
brainlid.org | ||
| | | | |
river.me
|
|
| | | | | RheingoldRiver's blog - MediaWiki development, Leaguepedia stories, and productivity hacks | |
| | | | |
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... | |
| | | | |
dankelley.github.io
|
|
| | | | | I just made a youtube video in which I show how to navigate through code using the neovim package called lunarvim. My test case is an R file. In a nutshell, I show two commands, each enabled by a few keystrokes. | |
| | | | |
osc.garden
|
|
| | | I copied Apple's UI/UX to gradually adjust my sleep schedule while handling every time zone quirk in the world (including that one island with 30-minute DST). | ||
