Remove Agile Remove API Remove Continuous Deployment Remove Open Source
article thumbnail

Embrace technical debt

Startup Lessons Learned

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

article thumbnail

Lessons Learned: Product development leverage

Startup Lessons Learned

In that same spirit, here are some suggestions for tactics you can use to increase the leverage of your product development efforts: Free and open source software (and even hardware ). When you participate in an open community like these you take advantage of tremendous amounts of effort. Expo SF (May.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Do lean startup principles have a place in the enterprise?

The Next Web

Facebook does it – they push new code to their platform at least twice a day and this includes changes to their API, which has over 40,000 developers using it for building apps. Here are a few pointers: Have your developers use agile development – they will love you for it. Consider open-sourcing certain aspects of your platform.

Lean 132
article thumbnail

Lessons Learned: Sharding for startups

Startup Lessons Learned

A given customer would have an entity URL that looked like this: customer://1234 Somewhere in your API, you have a way to access data about a given customer. Whichever API you use, URL-based sharding is very easy to understand. The better your internal APIs and data architecture, the easier this step will be.

article thumbnail

Lessons Learned: Why PHP won

Startup Lessons Learned

When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. And I think a bad choice, a bad library, a horrible API, lack of documentation etc. Case Study: Continuous deployment makes releases n. will make the foundation weak.

PHP 166