article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

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.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: Great open source scalability tools from Danga

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: Sharding for startups

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

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.

CTO 168
article thumbnail

Learning from Obama: maneuver warfare on the campaign trail

Startup Lessons Learned

Obama understood the two concepts that are essential for building a high-performance, highly adaptable, agile organization: 1) rapid iteration and 2) clear values-based objectives. That voter database was accessible to staff at every level of the campaign. Case Study: Continuous deployment makes releases n. Expo SF (May.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

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.