Startup Lessons Learned

SEPTEMBER 5, 2008

MogileFS - "Distributed (meta) file system. link] And - of course - going through [link] and reading up on the various different approaches different companies have (successfully) taken towards getting scalability at reasonably low cost. Case Study: Continuous deployment makes releases n. Pay less for storage.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

MARCH 22, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection. The cost will be felt in jobs -- thousands of new jobs that could have been created here, but werent. Case Study: Continuous deployment makes releases n.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

JANUARY 2, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an internet connection. This is just like a startup to me, complete with distribution and product development challenges, ecosystem design and many, many customers.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

AUGUST 1, 2009

Which comes to the second major principle: halt work that leads to more waste, even if it means abandoning sunk costs. Just because something looks pretty, or feels like a good idea, or has a lot of sunk cost in it, does not mean it should be pursued. This is a version of the andon cord technique from lean manufacturing.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

APRIL 26, 2009

Plus, we saw some of the intrinsic limitations of supporting such a large staff: slower cycle times, higher cost basis, and - most importantly - the ability to serve only a limited number of customer segments. That engine of creativity has led to a catalog of something like 2 million virtual goods authored by a hundred thousand developers.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Lean startups have the ability to use this commodity stack to lower costs and, more importantly, reduce time to market.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

AUGUST 24, 2009

One is explaining the world as it used to work: the importance of gatekeepers, the scarcity implied by limited distribution, and the resulting quality bar that the industry is so proud of. Mostly it is the time and expense required to create the means of distribution for that industry. It’s just taking some longer than others.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

SEPTEMBER 8, 2008

It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. I cant really imagine how much it cost our "grownup" counterparts at other dot-com startups to get their first app up and running. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 2, 2008

Or your cost of customer acquisition just magically floats up to match your customer lifetime value. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. we dont talk enough about how it feels.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

APRIL 14, 2009

This is an incredible skill, one that most engineers overlook. Because they have no presence in the market, they have to find distribution channels to bring in customers. They know how much it costs to bring in a customer and they know how much money they can expect to make on each one. involved before we go into production.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 12, 2009

At IMVU, when wed hire a new engineer, we could get them to ship code to production on their first day, even if they had never programmed in PHP before. For most of its existence, PHP didnt have a standard package-distribution system or very good module support. Yes, Python developers DO tend to cost more.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

NOVEMBER 5, 2013

Kent Beck of Facebook will give a talk and lead a discussion on how engineers in particular can simultaneously experiment and execute in companies that have enough success they now need to do both. John Goulah will show you how Etsy gets engineers on board with continuous deployment, an important technical environment that many resist.

Lean 166

Lean Early Stage San Francisco Cofounder 166

Startup Lessons Learned

JANUARY 4, 2009

This has two major drawbacks: the central directory can become a single point of failure, and there is a performance cost for having to consult the directory ever time you want to access data anywhere in the cluster. This is great for something like a huge DHT or a distributed work queue.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

OCTOBER 23, 2009

We backed into prices from all sorts of angles, estimating the time-cost of equivalent functionality, competitive offerings, other tools we were potentially displacing -- but in the end, we lobbed a few numbers at them and waited to see if they flinched. We walked them through what we thought would be the major application of our product.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

SEPTEMBER 11, 2009

This single decision wound up costing the company significant revenue and over the course of several months sent its customer growth into decline. In the end, we managed to repair the damage, but only after losing a lot of time and at significant opportunity cost. Case Study: Continuous deployment makes releases n.

Community 158

Community Management Lean Software Review 158