Architecture Continuous Deployment Distribution Engineer 
Startup Lessons Learned
SEPTEMBER 7, 2008
Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Its a nice complement on the product engineering side to his customer development methodology.
Startup Lessons Learned
SEPTEMBER 30, 2008
So I initially gravitated to the CTO title, and not VP of Engineering. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. They might do anything !
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 2, 2008
We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. Labels: agile , continuous deployment 1 comments: timothyfitz said. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
SEPTEMBER 8, 2008
You dont need to invent a new architecture, and you dont need to even build your architecture up-front. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. yeah, its awesome.
Startup Lessons Learned
APRIL 26, 2009
We combined three tactics: extensive use of free software, an open platform for user-generated content, and leveraged distribution channels. That engine of creativity has led to a catalog of something like 2 million virtual goods authored by a hundred thousand developers. Leveraged distribution channels.
Startup Lessons Learned
JANUARY 4, 2009
Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.
Startup Lessons Learned
SEPTEMBER 22, 2008
Lots of engineers are busy checking in and deploying their work. Someone has managed to convince themselves that they have to do their big architecture change in one fell swoop. Sure, we kept that one engineer busy while they toiled away on their own, but did that optmize the whole teams efforts?
Expert insights. Personalized for you.
131 
Let's personalize your content