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
But I have a special sympathy for the "product manager" in a startup that is bringing a new product to a new market, and doing their work in large batches. 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.
mashable.com
OCTOBER 27, 2010
TheyMakeApps.com is a good resource if you’re looking for a competent mobile dev agency. Here, developers and dev shops are organized by vertical so you can find a shop that has expertise in the kind of app you want to build. View More » Jobs VP of Sales at Mashable (New York, Ne. PM OK, agree.
mashable.com
MAY 9, 2011
a New York-based sizzle reel production company specializing in promotional videos for PR and marketing professionals, and the Young Entrepreneur Council. When making technical hires, we always reach out to our network of programmer friends and ask them to sit in on interviews and review resumes with us.
Up and Running
MAY 6, 2015
The first article that we wanted to talk about is one written by the founder of Palo Alto Software, Tim Berry. Your accounting software, you’re entering those numbers. Twenty-three year-olds in New York City running a small business. We get to read articles on Bplans all day and pretty much comment on them.
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.
Expert insights. Personalized for you.
161 
Let's personalize your content