Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Expo SF (May.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

OCTOBER 20, 2008

If engineers want more time to spend making their old code more pretty, they are invited to do so on the weekends. The idea is that once we move to the new system (or coding standard, or API, or.) The current code is spaghetti, but the new code will be elegant. Its become "legacy code" and part of the problem.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

OCTOBER 5, 2008

Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. In exchange, the team agrees to show each piece of working code to the product manager for his approval.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thank you. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 10, 2009

Our code pushes take another six minutes. Since these two steps are pipelined that means at peak we’re pushing a new revision of the code to the website every nine minutes. On average we deploy new code fifty times a day. Code reviews and pairing Great practices. Throwing out a lot of code.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

DECEMBER 7, 2008

When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. He throws off volumes of code, and it works.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. This shift allowed us to crank out working software quickly as a service.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

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. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JULY 29, 2009

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. But there is more to technical debt than just the interest payments that come due. The failure of the feature had nothing to do with the quality of the code.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Both Sides of the Table

JUNE 22, 2011

But a certain amount gets lost in the headlines – especially when not everybody actually heard the video and knows the nuance of the message. It’s like people arguing that there’s a beautiful beach house in 2006 that represents great long-term value due to scarcity of similar property. Fair enough.

Saudi Arabia 309

Saudi Arabia Valuation IPO Technical Review 309

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. The Lean Startup Intensive is tomorrow at Web 2.0.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

MAY 31, 2010

Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. Sean Murphy has an excellent and comprehensive roundup of resources about the conference: all of the slides, videos, summaries, notes and write-ups are listed on his blog here.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

crowdSPRING Blog

MARCH 28, 2013

Every day on the crowdSPRING Twitter account and on my own Twitter account , I post links to posts or videos I enjoyed reading or viewing. These posts and videos are about logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, and more! Lean Business: Freelancers for ALL My Friends!

Social Media 107

Social Media Small Business Design Media 107

Startup Lessons Learned

AUGUST 2, 2008

Your natural tendency when an investor says yes will be to relax and go back to writing code. The Lean Startup Intensive is tomorrow at Web 2.0. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May. Expo SF (May.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

MAY 7, 2009

Getting features and fixes into hands of users was the greatest priority - a test environment would just get in the way and slow down the validation coming from having code running in production. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day. Heres the key point.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

JANUARY 12, 2009

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. Every change required a server restart.

PHP 166

PHP Software Review Ruby San Francisco 166

Steve Blank

SEPTEMBER 14, 2009

On top of all this it was considered very bad form not to have at least four additional consecutive quarters of profits after an IPO.) The IPO Bubble – August 1995 – March 2000 In August 1995 Netscape went public, and the world of start ups turned upside down. Tech acquisitions went crazy at the same time the IPO market did.

Silicon Valley 230

Silicon Valley IPO Technical Review Venture Capital 230

Startup Lessons Learned

JUNE 17, 2010

Then we’d build the feature, which would often include tools that were intended for the art team to use to build the parts of the product that they were responsible for (in video game parlance, this is the “art path&# that allows artists to get their work into the production product). I remember one such meeting vividly.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

online.wsj.com

SEPTEMBER 23, 2012

Computer Software. Media & Marketing. Small Business. More Industries. Accounting. Advertising. Broadcasting & Entertainment. Computer Hardware. Consumer Products. Defense & Aerospace. Financial Services & Insurance. Food & Tobacco. Hospitality. Industrial Goods & Services. Marketing & Strategy. Media Agencies. Metals & Mining. NAME Comcast.

Venture Capital 107

Venture Capital Software Review Rhode Island North Dakota 107

crowdSPRING Blog

SEPTEMBER 28, 2012

Every day on the crowdSPRING Twitter account and on my own Twitter account , I post links to posts or videos I enjoyed reading or viewing. These posts and videos are about logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, and more! lean Democrat – [link].

Social Media 95

Social Media Small Business Design Media 95

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. October 4, 2008 10:33 AM Amitt Mahajan said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

FEBRUARY 22, 2009

See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? These were primitive open-ended video games created by the players themselves , using simple programming languages. DRM and other restrictions.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

www.vccafe.com

MARCH 11, 2013

VC Cafe highlights everything you need to know from hosting your code in hackathons to open source legal docs. Lean Methodology Sources. Steve Blank on Lean Customer Development. Part 3- Lean Cust. Videos/presentations. Use us to power any video chat applications (talkshow, education apps, collaboration, etc).

Software Review 53

Software Review Technical Review Startup 53

Startup Lessons Learned

OCTOBER 5, 2009

Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. I have detected a secret virus in your CPU. The curse of prevention Beware!

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

MARCH 3, 2009

At IMVU , these were quite common (after all, were shipping code 50 times a day). They are collected and reviewed after an appropriate interval (e.g. In response to Sean - Intel still runs a very formal process of setting expectations, evaluating employees and reviewing progress on a quarterly basis. love your openness at IMVU.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

SEPTEMBER 27, 2010

Over time, such teams either explode due to irreconcilable differences or dramatically slow down. As I found out to my dismay, this is a dangerous game: in many cases, you’re asking trained professionals to violate their own code of best practices, for the good of the company. Any excesses are likely to be moderated by others.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Both Sides of the Table

JULY 16, 2010

You don’t need to buy expensive software – there are free open source solutions for nearly everything. Staying “lean&# is not an option. You invest low amounts of capital and the company gets to IPO (96-99) or trade sale (05-08) without raising too much capital and certainly not on punishing terms.

LP 311

LP Technical Review Early Stage Silicon Valley 311

Startup Lessons Learned

JULY 5, 2010

When I wrote a review of Four Steps on this blog in November, 2008, I did my best to be candid and warn of a few shortcomings: And Steve is the first to admit that its a "turgid" read, without a great deal of narrative flow. Four Steps primarily centers its stories and case studies on B2B hardware and software startups.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

JANUARY 30, 2009

Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. As we move into a new economic climate, its my hope that our industry will stop this expensive kind of learning and start building lean startups instead. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

AUGUST 26, 2009

If you watch the video/audio below, youll get to see some of the questions I was asked after my presentation. I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

FEBRUARY 16, 2009

This is a great example of lean startup thinking. Lets start with a distinction between shipping new software to the customer, and changing the customers experience. The idea is that often you can change the customers experience without shipping them new software at all.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Up and Running

JUNE 13, 2015

What Daniel Coyle, the author of, The Talent Code, calls a “Deep practice,” I think of it as painful practice because it’s a little bit uncomfortable. At the time of their IPO, Groupon was valued at $13 billion. They’re out of work and Michael was kind enough to give the review and a recommendation for that book.

Video 60

Video Burundi South Africa Portfolio 60