Remove Continuous Deployment Remove Database Remove Metrics
article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Case Study: Continuous deployment makes releases n.

article thumbnail

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

Startup Lessons Learned

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?

Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

Massive proprietary databases? Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Case Study: Continuous deployment makes releases n. I dont think so.

CTO 168
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: Lean hiring tips

Startup Lessons Learned

This is another sub-optimization caused by incentivizing the wrong metric. 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.

Lean 140
article thumbnail

Lessons Learned: The hacker's lament

Startup Lessons Learned

For this product, I later realized that I was the software architect, the frontend engineer, the backend engineer, the database administrator, the systems administrator, the QA engineer, and lastly I was the only technical support guy. Case Study: Continuous deployment makes releases n.

article thumbnail

Learning from Obama: maneuver warfare on the campaign trail

Startup Lessons Learned

Observe At the end of each day, wed laboriously enter data, updating the campaigns voter database with information about every voter contact we accomplished that day. That voter database was accessible to staff at every level of the campaign. Case Study: Continuous deployment makes releases n.