Explore >> Select a destination
|
You are here 
|
sidneyliebrand.io | ||
| | | | |
ctoomey.com
|
|
| | | | | [AI summary] An article detailing a personal, incremental, and experimental approach to learning and configuring Vim text editor based on a talk by Chris Toomey. | |
| | | | |
www.brandonpugh.com
|
|
| | | | | Last weekend I attended the Global Day of Coderetreat in Dallas, TX which was not only my first Coderetreat but also my first time attending a developer community event and I have to say that it was a great and worthwhile experience. If you're unfamiliar with the format of a Coderetreat you can read all about it at coderetreat.com but its basically a code kata where you spend most of the day pairing up in 45 min sessions and attempt to solve Conway's Game of Life (a fascinating problem by itself). I had only first heard about it a couple weeks before when Corey Haines went on the Herding code podcast to talk about it and I'm glad I went because I feel took away a few key benefits. | |
| | | | |
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... | |
| | | | |
ashishvegaraju.com
|
|
| | | In this article, I will demonstrate how to write testable code using TypeScript. I assume that the reader is familiar with JavaScript, heard about Typescript... | ||
