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.
Startup Lessons Learned
SEPTEMBER 10, 2008
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuous deployment, see Just-in-time Scalability.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.
Startup Lessons Learned
SEPTEMBER 30, 2008
Massive proprietary databases? Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases.
Startup Lessons Learned
OCTOBER 20, 2008
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Case Study: Continuous deployment makes releases n.
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