Continuous Deployment Database Development Team Review Programming 
Startup Lessons Learned
OCTOBER 20, 2008
When I was working my first programming jobs, I was introduced to the following maxim: "time, quality, money - pick two." As I evolved my thinking, I started to frame the problem this way: How can we devise a product development process that allows the business leaders to take responsibility for the outcome by making conscious trade-offs?
Startup Lessons Learned
DECEMBER 7, 2008
TDD plus continuous integration works as a natural feedback loop: if the team is working "too fast" to produce quality code reliably, tests fail, which requires the team to slow down and fix them. Use pair programming and collective code ownership. Pair programming is the most radical, but also the most helpful.
Expert insights. Personalized for you.
164 
Let's personalize your content