Cofounder Continuous Deployment Database Design 
Startup Lessons Learned
SEPTEMBER 10, 2008
But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Do you have a bug database?
Startup Lessons Learned
SEPTEMBER 30, 2008
So what does CTO mean, besides just "technical founder who really cant manage anyone?" If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Massive proprietary databases? I always assumed I wouldnt manage anybody. I dont think so. Great piece!
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JANUARY 19, 2009
Returning to our example of the beleaguered founder who still has the pager, before hiring an operations guy, try promoting someone from within to take on the job. They maintain a huge database of passive candidates, by offering to pay them when they interview. Particularly the Continuous Deployment and Split testing posts.
Startup Lessons Learned
OCTOBER 20, 2008
*All* of the factors involved in delivering software are affected by starting with baseline requirements that are constrained to what the system should do and the process artifacts desired (say 5 forms reading and writing a database store). For many projects, customer approval and sign off was required as well.
Startup Lessons Learned
OCTOBER 19, 2009
Then, the company spends no more than a few hundred dollars marketing the product through search engines and to the contacts in its sales database and LinkedIn. We do not develop a product until we get a paying customer," says Orit Pennington , who co-founded the six-employee company with her husband in 2002.
Startup Lessons Learned
MAY 1, 2009
Heres the working definition Ive started using: A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty. You mentioned as many as 50 deployments a day to production after successful local continuous integration. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
NOVEMBER 13, 2008
Wish I could figure out how to apply it to the average data warehousing project which has a single shareed database right at the heart of the entire solution. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
144 
Let's personalize your content