This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
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."
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.
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? Labels: agile , continuousdeployment , customer development , events , listening to customers , slides 3comments: Sean Murphy said.
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." You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth."
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. Case Study: Continuousdeployment makes releases n. I was building a new startup in 1999, and wanted to do it right.
Someone has managed to convince themselves that they have to do their big architecture change in one fell swoop. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content