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

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did).

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Steve Blank

OCTOBER 30, 2012

The class teaches founders how to dramatically reduce their failure rate through the combination of business model design, customer development and agile development using the Startup Owners Manual. If you can’t see the video above click here.). You present your hypotheses and what you learned in front of your peers and coaches.

Startup 335

Startup Lean Incubator Business Model 335

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?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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

Hearpreneur

DECEMBER 29, 2021

Websites like Udemy, YouTube, and LinkedIn Learning are chock full of short video tutorials to help keep your ingenuity sharp and ready. The year 2021 has presented a lot of business opportunities for us and we have successfully established our workflow and protocols. This will help those who lost work due to the pandemic.

Entrepreneur 139

Entrepreneur Social Media Employee Los Angeles 139

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. For software, the easiest batch to see is code. Every time an engineer checks in code, they are batching up a certain amount of work. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Agile VC

MAY 13, 2013

If you think back to the monster consumer software and internet companies that’ve been built in the last 2-3 decades, it’s actually far more likely they were fast and/or particularly innovative followers rather than first movers. Atari (home video game consoles). Netflix (video streaming). First Movers.

Cloud 205

Cloud B2B Software Review Technical Review 205

Austin Startup

AUGUST 23, 2017

Recently many of us dedicated our Saturday attending and presenting at the biannual un-conference, ProductCamp. Upgrade From This Old Unnecessary Process David Hawks , CEO, Agile Velocity Main take-away — focus on discovery, not as much delivery. Most of the Agile world is in the perspective of delivery focus. User Stories Suck!

Austin 48

Austin Technical Review Agile SQL 48

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

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

MAY 31, 2010

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. All video from the conference is available for free at Justin.tv And a special thanks is due to all of our presenters, panelists, and mentors.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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

AUGUST 2, 2008

Your natural tendency when an investor says yes will be to relax and go back to writing code. ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

ConversionXL

NOVEMBER 9, 2017

It’s not just “how to tie a tie” how-to videos, it’s also learning hard skills. People learn best when the material is presented to them in a specific way. The Society for the Teaching of Psychology explains how they work: “At a conceptual level, mnemonics bolster memory due to at least three factors.

Retention 106

Retention Software Review Agile Video 106

Hearpreneur

AUGUST 11, 2021

With a simple 30 second video posted on social media, business owners have the opportunity to build major traffic and revenue from their sites. In practice, entrepreneurship and innovation will not present themselves in the same way in future economic systems. The necessities will be driven by execution and leadership.

Entrepreneur 127

Entrepreneur Technical Review Social Media Bootstrapping 127

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

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

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

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. We changed our model to B2B and adopted Agile around 2002. May 15, 2009 5:59 PM Eric said.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

SEPTEMBER 15, 2008

To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. It was actually my co-founder Will Harvey who taught me to present this data in the simple format weve discussed in this post. Code To make split-testing pervasive, it has to be incredibly easy.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Occam's Razor

APRIL 15, 2019

The average length of our video ads is 30 seconds, less than 10% of the audiences watches beyond 5 seconds and 90% is exposed to less than 1 second. Factually presented. Present the collection directly to the Rationalizer if you can. During 2019, our Net Promotion Score has dropped 15 points. Negative data. Accurately collected.

Leadership 80

Leadership Non-Compete Analytics Software Review 80

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. Expo SF (May.

Customer Development 166

Customer Development Developer San Francisco Customer 166

YoungUpstarts

NOVEMBER 5, 2020

Software and Equipment. Access to the appropriate IT software and equipment should be a necessity when working from home, but due to the rushed nature of many remote working schemes, for many this was not an initial focus. An array of essential data will be present in any business, regardless of size.

Technical Review 246

Technical Review Software Review Security Agile 246

Up and Running

MAY 23, 2016

Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. If you use software like LivePlan, you can create this initial “lean plan” in under an hour and then spend your time where it really matters—on validating your idea.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

AUGUST 24, 2009

So let’s turn our attention from what may happen in the future to what is definitely happening in the present. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. Even if a self-published book was every bit as good as one published by a top-tier press, how would the reviewers know?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

ConversionXL

NOVEMBER 29, 2017

First, there are costs that we incur by testing , regardless of the outcome, such as paying for testing tools, for developing, designing and QA-ing test variants, for the analysis time and software, etc. Some software use two-tailed tests, while others use one-tailed tests. Do you know which one is your software reporting?

Software Review 112

Software Review Cost Conversion Software 112

ConversionXL

NOVEMBER 10, 2020

Have you checked out this blog post, this video, and this infographic? We might have medium-term goals like “adopting agile methodologies” or “getting everyone on the same page with a project kick-off” as the outcomes for the reader. The Agile Coach includes a mix of long-form articles, vidoes, and tutorials.

Agile 139

Agile Social Media Audience Software Review 139

andrewchenblog.com

MARCH 10, 2010

You often end up with lots of half-done experiments lying around, an infrastructure that isn’t built to scale, and a mishmash of code that needs to be refactored. For example, a design approach just turns out to be error-prone or a junior programmer just writes bad code. Of course, we are mostly interested in the second type.

Technical Review 47

Technical Review Design Las Vegas Product 47

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

MARCH 4, 2009

Today, Id like to spend some time on two techniques: the problem presentation and learning what channels of information reach customers. It connects to the internet to automatically download the necessary codes. If you are grappling with understanding what problem your product solves, try building a "problem presentation."

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

NOVEMBER 13, 2008

A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

SoCal CTO

DECEMBER 1, 2010

The United States is now a debtor nation to China and that the bill is about to come due. Five Reasons You Haven’t Launched - Software By Rob , November 10, 2010 Photo by stevendepolo. These are probably the two sites where I've posted the most reviews. This Thanksgiving it might seem that there’s a lot less to be thankful for.

Technical Review 175

Technical Review Technology Product CTO Hire 175

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

AUGUST 3, 2009

Below youll find the video of my remarks as well as the full slides embedded below. Without further ado, the video: Slides are below: Minimum Viable Product View more presentations from Eric Ries. Labels: minimum viable product , slides , video 13comments: Alan Pinstein said. But I wanted to say a few words first.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168