Architecture Continuous Deployment Lean 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. Just what is the CTO supposed to do?
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. Expo SF (May.
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. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.
Startup Lessons Learned
JANUARY 30, 2009
Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Even a great architecture becomes inflexible.
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. One major theory that has influenced the way I think about processes comes from Lean Manufacturing , where they use these same techniques to build cars. Expo SF (May. for Harvard Business Revie.
Startup Lessons Learned
JULY 29, 2009
I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Outside the world of hypothetical examples, its more important to make continual progress than to build the ultimate design. It was still a good trade.
Startup Lessons Learned
JUNE 17, 2010
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. So this time, they are going to spell out what’s important in even greater detail, to leave less wiggle room.
Expert insights. Personalized for you.
168 
Let's personalize your content