Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. August 8, 2009 6:08 AM Phil Winkler said. August 8, 2009 5:04 PM PetrolHead said. But what about Commodity?

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JUNE 17, 2010

I suggested that we change the underlying architecture of our UI system so that the artists would be able to build their own UI pieces themselves and then integrate them into the product without requiring new code every time. The engineering team wasn’t happy either. The engineering team wasn’t happy either.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

DECEMBER 28, 2009

Lessons Learned by Eric Ries Monday, December 28, 2009 Continuous deployment for mission-critical applications Having evangelized the concept of continuous deployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it. Monitoring of real-world metrics.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

SEPTEMBER 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Were in a new wave of platform evolution.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

www.subelsky.com

FEBRUARY 25, 2010

Mike Subelskys Blog Wednesday, November 11, 2009 Lean startup tools for Rails apps A few months ago I was invited to dinner with the Geeks on a Plane crew when they stopped in Washington, and had the opportunity to meet one of my heroes, Eric Ries , author of the Startup Lessons Learned blog. November 30, 2009 10:46 AM charliepark said.

Lean 41

Lean Baltimore Ruby Maryland 41

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. Open APIs and data-oriented architecture (aka "web 2.0"). April 27, 2009 10:54 AM DSarathy said. Great post! hadnt heard of that before. Very useful post.

Product Development 88

Product Development Developer San Francisco Product 88

dontbesoanalytical.blogspot.com

MAY 13, 2012

Inside the development organization, this Director attends to staffing, training, workload and productivity metrics, budget, and scheduling. The CTO needs to understand the abstract potential that a new technology might offer, and must know the underlying architecture of the firm’s business processes. ► 2009. (2).

CTO 40

CTO Technical Review Technology Software Review 40

ConversionXL

MARCH 19, 2020

The questions that clients ask in the coming months are going to be more focused on business results and less on trends and vanity metrics. recession in 2009.”. Use a down period to nail down the core product features, get your architecture right and make sure your first customers see value in the product.

Marketing 121

Marketing Campaign Non-Compete Lean 121

Occam's Razor

JANUARY 20, 2010

End of a minor web analytics lesson on going beyond obvious metrics and never, ever, never forgetting context. Of course look at our favorite metric bounce rate by keyword (that tells you if you can get people to give you one solitary click , the most primitive measure of SEO success). " In April 2009!! Back to our story.

Analytics 90

Analytics Search SEO Metrics 90

Startup Lessons Learned

OCTOBER 5, 2009

Lessons Learned by Eric Ries Monday, October 5, 2009 The curse of prevention Beware! It’s important to invest in good architecture so that your website will scale once customers arrive. In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. Why do they harbor that paranoia?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Steve Blank

NOVEMBER 30, 2009

One of the times I screwed this up it left a legacy of 25 years of questionable design in microprocessor architecture. » 25 Responses Mark Soper , on November 30, 2009 at 6:55 am Said: Steve, I’m working on a consumer internet product concept at the customer discovery phase. It’s an art.

Customer Development 283

Customer Development Developer Customer Silicon Valley 283

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. July 13, 2009 7:38 AM George said. July 13, 2009 10:32 AM Anonymoussaid.

Product Development 153

Product Development Developer San Francisco Product 153

andrewchenblog.com

MARCH 10, 2010

For entrepreneurs out there who are building metrics-driven products but also committed to a great user experience, I would love to hear when and how you pay down the product design debt. By the way, to mitigate this problem, there's already a discipline called “Information Architecture&#. Please comment! what a coincidence.

Technical Review 47

Technical Review Design Las Vegas Product 47

Cracking the Code

FEBRUARY 12, 2007

► 2009. (9). SaaS business metrics: why are they different? on a scale of 1-4). ► 03/07 - 03/14. (1). State of the SaaS 13: Q1 2010 Sentiment. ► 02/21 - 02/28. (1). A funny perspective on Google innovation. ► 01/10 - 01/17. (1). Happy New Year 2010! ► 11/29 - 12/06. (1). ► 11/08 - 11/15. (2).

Software Review 48

Software Review SEM Marketing Las Vegas 48

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Cracking the Code

DECEMBER 16, 2006

► 2009. (9). SaaS business metrics: why are they different? He is a great speaker and I enjoyed the speech, but after 40mn, I was still waiting to hear about the future of software. ► 03/07 - 03/14. (1). State of the SaaS 13: Q1 2010 Sentiment. ► 02/21 - 02/28. (1). A funny perspective on Google innovation.

Software Review 48

Software Review Silicon Valley Technical Review Software 48

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. February 11, 2009 8:05 AM Anonymoussaid.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 29, 2008

and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture? Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. I remember answering "What security model?"

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. February 17, 2009 9:48 AM Kevin Gadd said.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 8, 2009

Lessons Learned by Eric Ries Tuesday, September 8, 2009 What would you want to tell Washington DC about startups? September 8, 2009 6:12 PM Geoff Hsaid. September 8, 2009 6:25 PM dbsaid. September 9, 2009 12:36 AM Richard Tibbetts said. September 9, 2009 5:05 AM Roger Toennis said. Agree with all your points.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding. Its common to find a hacker at the heart of almost any successful technology company.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

SEPTEMBER 22, 2008

Someone has managed to convince themselves that they have to do their big architecture change in one fell swoop. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Take a look and let me know what you think.

Product Development 68

Product Development Developer San Francisco Product 68

Cracking the Code

OCTOBER 10, 2008

Effectively measuring and understanding your CAC and CLTV metrics are key to future success. Bessemer SaaS Law #1: Your key monthly business metrics are: CMRR (Committed Monthly Recurring Revenue), Churn, and Cash flow - “Bookings” is for suckers. Brian, Paglo www.paglo.com. Great list! Great list! Philippe Botteri.

Software Review 48

Software Review North America Europe Metrics 48

Startup Lessons Learned

JANUARY 30, 2009

Lessons Learned by Eric Ries Friday, January 30, 2009 Achieving a failure We spend a lot of time planning. Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Even a great architecture becomes inflexible. Great post!

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

Lessons Learned by Eric Ries Wednesday, January 28, 2009 Refactoring yourself out of business Let me start out by saying I am a big fan of refactoring , the ongoing process of changing code so that it performs the same behaviors but has more elegant structure. January 29, 2009 12:08 AM Mahesh said. Doesnt that sound good?

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

www.rocketwatcher.com

DECEMBER 5, 2011

Most startups start out with only 1 or 2 offerings and often aren’t thinking about how things might fit into a naming architecture. About Rocket Watcher Rocket Watcher is my personal blog covering marketing for startups including messaging, market strategy, lead generation and metrics. December 2009. November 2009.

Naming 41

Naming Startup Product Name Framework 41

blog.expensify.com

APRIL 24, 2012

The vast majority of patterns and architecture patterns that we see in PHP, Ruby and other scripting languages are incomplete implementations of stuff the Java and C# guys created. In March 2009, they launched a Beta version and demoed it at FinovateStartup 2009.” I wrote in assembly, understood optimizations.

Java 107

Java PHP Software Review Coder 107

VC Cafe

JANUARY 16, 2011

Previous Israeli exhibitors lists are available MWC 2009 and MWC 2010. The solution provides a live, accurate status of customers’ level of satisfaction, according to metrics that are pre-defined and measured at the time of the customer experience. The modular architecture and scalability of the solutions enables.

Mobile 103

Mobile Securities and Exchange Commission Flash IP 103