Startup Lessons Learned
SEPTEMBER 30, 2008
Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? Often times, it seems like people are thinking its synonymous with "that guy who gets paid to sit in the corner and think technical deep thoughts" or "that guy who gets to swoop in a rearrange my project at the last minute on a whim."
www.lanceglasser.com
MAY 13, 2012
What does a CTO do? Thank you Japan. What does a CTO do? What does a CTO (Chief Technology Officer) do in a high-tech company? So what is the CTO job? The best description of this was given to me by my friend Greg Papadopolous who was on the faculty at MIT with me many years ago and is now CTO of Sun Microsystems.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 2, 2008
Lessons Learned by Eric Ries Tuesday, September 2, 2008 Just-In-Time Scalability At my previous company, we pioneered an approach to building out our infrastructure that we called "Just-In-Time Scalability." After all, the worst kind of waste in software development is code to support a use case that never materializes.
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. What about a hardware business with some long-lead-time components? Can this methodology be used for startups that are not exclusively about software? Take a look and let me know what you think.
Startup Lessons Learned
SEPTEMBER 8, 2008
So one of the first things we did was to hire an Oracle expert and get to work. You dont need to invent a new architecture, and you dont need to even build your architecture up-front. I was building a new startup in 1999, and wanted to do it right. I had heard that all great companies built their applications on Oracle.
Startup Lessons Learned
DECEMBER 7, 2008
I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Just change it.
Startup Lessons Learned
SEPTEMBER 22, 2008
Someone has managed to convince themselves that they have to do their big architecture change in one fell swoop. When Ive worked to get everyone to build in small batches, I would see this pattern in action. Lots of engineers are busy checking in and deploying their work. Take a look and let me know what you think.
Expert insights. Personalized for you.
168 
Let's personalize your content