Architecture Continuous Deployment Management Technology 
Startup Lessons Learned
SEPTEMBER 30, 2008
What does your Chief Technology Officer do all day? When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. I mean, have you seen other people?
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. This engineering manager is a smart guy, and very experienced.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 8, 2008
Lessons Learned by Eric Ries Monday, September 8, 2008 Waves of technology platforms I still remember the first time I switched to LAMP. That startup didnt turn out so well, but not for lack of technology. You dont need to invent a new architecture, and you dont need to even build your architecture up-front.
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
JULY 29, 2009
Outside the world of hypothetical examples, its more important to make continual progress than to build the ultimate design. For example, at a previous virtual world company , we spent years developing an architecture to cope with millions of simultaneous users. That’s what Just-in-time Scalability is all about. One last thought.
Startup Lessons Learned
SEPTEMBER 7, 2008
We talk about taking advantages of the incredible agility offered by modern web architecture for extremely rapid deployment, etc. Labels: agile , continuous deployment , customer development , events , listening to customers , slides 3comments: Sean Murphy said. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JUNE 17, 2010
They are leaders, visionaries, founders and managers having tremendous success. The engineering team feels burned too, and feels that they were blamed for deficiencies in the spec as if it was their fault that the technology doesn’t really support what the artists want to do. Yet talent organized improperly can lead to failure.
Expert insights. Personalized for you.
168 
Let's personalize your content