Agile Continuous Deployment Database 
Startup Lessons Learned
NOVEMBER 13, 2008
Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. By the time we started doing continuous integration, we had tens of thousands of lines of code, all not under test coverage. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible.
Startup Lessons Learned
SEPTEMBER 10, 2008
I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. Do you have a bug database? Youd better.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 30, 2008
If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? And what about if deployment takes forever? Massive proprietary databases? Case Study: Continuous deployment makes releases n. But along the way, something strange happened.
Startup Lessons Learned
OCTOBER 20, 2008
When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.
Startup Lessons Learned
JANUARY 4, 2009
Data storage is becoming a specialized function, delegated most often to relational databases. If you are storing all of your data in a relational database, and the load on that database exceeds its capacity, there is no automatic solution that allows you to simply add more hardware and scale up.
Startup Lessons Learned
SEPTEMBER 5, 2008
For tips on how to integrate it into your database and application layers, you can see the tail-end of my JIT Scalability talk. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Expo SF (May.
Startup Lessons Learned
JANUARY 19, 2009
They maintain a huge database of passive candidates, by offering to pay them when they interview. Particularly the Continuous Deployment and Split testing posts. Case Study: Continuous deployment makes releases n. If you want to expand your pool of available passive candidates, give a site like NotchUp a try.
Expert insights. Personalized for you.
167 
Let's personalize your content