Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

JANUARY 27, 2009

I think a great example of freemium is 37signals' Haystack - they offer free listings to all designers, and premium listings that are larger, and have more pictures for $99 a month - thus increasing exposure for the paying customers. Case Study: Continuous deployment makes releases n.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

JANUARY 6, 2009

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. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 1, 2009

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. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 11, 2009

And if your app is designed to drive traffic to some off-network site or product, the cost is usually prohibitive, because the traffic in your app doesnt convert any better than a traditional CPM or CPC-based ad anywhere else on the network. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco Social Network Lean Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 13, 2008

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.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 29, 2008

Its nearly impossible to get a good read on all six attributes in a single interview, so its important to design an interview process that will give you a good sampling of data to look at. For example, I wold often work the circle-drawing question with candidates who only had ever programmed in a web-based scripting language like PHP.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JANUARY 4, 2009

Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start. It also doesnt make sense to design your app for scalability from the start, since you may have to create many iterations before you find a version that requires any scalability at all. 21comments: Imran said.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JANUARY 12, 2009

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. But by the time I was building my first websites for commercial use , PHP had taken over. Writing unit tests or mock objects in PHP is an exercise in constant frustration.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

JANUARY 30, 2009

Insist on high levels of usability, UI design, and polish. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. Departments were built and were even metrics-driven. But there was no feedback loop to help the company find the right metrics to focus on.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

I would also suggest, and the engineers will almost certainly hate this suggestion, that the decision-maker asks for hard metrics to justify the refactoring effort in the first place. Only one occasion was a substantial rewrite justified based on performance metrics. Case Study: Continuous deployment makes releases n.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79