Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. The idea is that once we move to the new system (or coding standard, or API, or.)

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. The product manager was clearly struggling to get results from the rest of the team. So why are they having so much difficulty?

San Francisco 158

San Francisco Management Software Review Product 158

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.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

rapidrollout.wordpress.com

JANUARY 15, 2011

Investors use a consulting CTO for technical due diligence. A consulting CTO is an expert on the current state of the technology and can suggest the most appropriate development platform for your business. Ask developers if they’ve been involved with a previous web startup and what their role was in the startup.

Fractional CTO 40

Fractional CTO CTO CTO Hire Fractional VPE 40

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

dontbesoanalytical.blogspot.com

MAY 13, 2012

Saturday, February 16, 2008. The CTO should not manage developers. The head of development spends his or her time working to keep the development team on track against a set of product plans. But if it’s wrong, the CTO has solid documentation to review. On the Use, and Misuse, of Software Test Metrics.

CTO 40

CTO Technical Review Technology Software Review 40

SoCal CTO

MARCH 22, 2007

We have been using LinkedIn for both sourcing recruits and reviewing backgrounds for recruits. ► February (2) CTO Founders / Cofounders Part-Time Startup CTO? ► January (5) Los Angeles Web Developer Startup CTO or Developer When to Use Facebook Connect – Twitter Oauth – Goo.

Technical Cofounder 150

Technical Cofounder Southern California Los Angeles CTO Hire 150