Development Team Review Hosting Software Review Sweden 
Startup Lessons Learned
FEBRUARY 20, 2009
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. The batch size is the unit at which work-products move between stages in a development process. For software, the easiest batch to see is code. I dont think so.
Startup Lessons Learned
OCTOBER 20, 2008
Even worse, when it comes time to "fix it right" the team gets pushback from the business leaders, who want more features. If engineers want more time to spend making their old code more pretty, they are invited to do so on the weekends. The idea is that once we move to the new system (or coding standard, or API, or.)
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 5, 2008
I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. Then the designs are handed to a team of programmers with various specialties.
Startup Lessons Learned
DECEMBER 7, 2008
When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. He throws off volumes of code, and it works.
blog.expensify.com
APRIL 24, 2012
The right sort of person is so passionate about coding, they can’t be stopped from doing it. But every day spent in that kitchen is a day NOT spent in a real kitchen, learning how to cook real food, and write real code. Full discloure, I am a former PHP, Perl, ColdFusion, ActionScript, VB.NET, ASP.NET and C# developer.
Expert insights. Personalized for you.
161 
Let's personalize your content