218 karma · joined August 10, 2010
1. Don’t ship any new features without writing unit tests for them first.
2. These new features most likely rely on parts of existing code so write a few tests for that existing code with each new feature.
3. If something breaks in production write a test for it at the time that you fix it.
Little by little you’ll increase your code coverage without grinding development to a halt.
What are some good machine translation sites?
- I decided to buck the trend of (1) co-host and instead went with having (2) co-hosts. One is a designer, the other is a dev/designer, and I'm mostly dev.
- I was inspired to start the podcast while watching Kevin Roses's 2009 FOWA presentation where he said all startups should be doing one.
- Between Tumblr & Feedburner it's incredibly easy to do one.
- I found that the mic in my MBP isn't quite good enough so I ordered a Rode Podcaster that I hope will get here in the next day or so.
I'm looking for some constructive feedback from the incredible HN crowd. Thanks