This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Lessons Learned by Eric Ries Monday, June 15, 2009 Why ContinuousDeployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuousdeployment , a process that allows companies to release software in minutes instead of days, weeks, or months.
Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuousdeployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. Our code pushes take another six minutes.
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.
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuousdeployment, see Just-in-time Scalability.
Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? But I dont think most startups really have a need for someone to do that on a full time basis. It became harder and harder to separate how the software is built from how the software is structured. Massive proprietary databases?
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. The idea is that once we move to the new system (or coding standard, or API, or.)
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuousdeployment , just-in-time scalability , and even search engine marketing , to name a few. This is easiest to see in deployment.
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.
Lessons Learned by Eric Ries Monday, February 16, 2009 Continuousdeployment with downloads One of my goals in writing posts about topics like continuousdeployment 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.
But I have a special sympathy for the "product manager" in a startup that is bringing a new product to a new market, and doing their work in large batches. Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. one more thought, where were the codereviews?
Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.
I spent some time with his company before the conference and discussed ways to get started with continuousdeployment , 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 continuousdeployment is feasible.
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).
Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on.
But there is more to technical debt than just the interest payments that come due. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. In particular, try these three things: Invest in technical debts that may never come due.
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. They share a common language, culture, and coding style.
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.
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. .
This post was written by Sarah Milstein, co-host of The Lean Startup Conference. We’re looking for speakers for the 2013 Lean Startup Conference. If you’re a Lean Startup veteran, feel free to skim the beginning, as this is mostly stuff you already know. Last week, we announced that our short application form was live.
Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. The Hackers Guide to Investors [link] Whatever help investors give a startup tends to be underestimated.
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. First of all, why split-test?
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. Those who have the endurance are the ones that tend to lead teams and join startups, because you just cant be successful in a startup situation without empathy.
Startups are companies. Startups aspire to become big companies. Therefore, startups should have departments. Each of these benefits also exists in startups, which is why most startups are also organized in departments. I once worked at a startup with an exceptional functional department system.
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. First, a caveat.
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? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Can I send you a review copy?
Lessons Learned by Eric Ries Wednesday, August 26, 2009 Building a new startup hub Last week, I had a unique opportunity to spend some time in Boulder at the behest of TechStars. It was a great experience to see a relatively new startup hub in action - and thriving. Their model looks like a key ingredient in the startup brew there.
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. There are just so many ways for a startup to fail.
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.
Lessons Learned by Eric Ries Tuesday, March 3, 2009 Employees should be masters of their own time Every startup should have a culture of learning. Without entering into that theoretical domain, in this post Id like to try and offer a specific and concrete suggestion for how to build a culture of learning into a startup.
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 codereviews more seriously than any other company Ive even heard about. No departments The Five Whys for Startups (for Harvard Business R.
Over time, such teams either explode due to irreconcilable differences or dramatically slow down. Yet startups rely on collective learning in order to find their way. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal. Of course, this logic applies to members of all factions.
Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. First of all, the Startup Lessons Learned conference exceeded my wildest expectations. And a special thanks is due to all of our presenters, panelists, and mentors.
I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups.
Lessons Learned by Eric Ries Friday, March 27, 2009 Cash is not king Cash on hand is just one important variable in a startup’s life, but it’s not necessarily the most important. These successful startups managed to have enough tries to get it right. A checklist of practices in the new Joel Test for Startups.
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. I joined a financial services tech startup in 1999. It was a disaster.
Lessons Learned by Eric Ries Monday, December 14, 2009 Business ecology and the four customer currencies Lately, I’ve been rethinking the concept of “business model&# for startups, in favor of something I call “business ecology.&# A successful startup strives for this latter case. Successful startups don’t.
These posts and videos are about logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, and more! Small Business and Startups: For Great Customer Service, Speed Counts – [link]. Small Business and Startups: For Great Customer Service, Speed Counts – [link].
In other words, they are facing conditions of extreme uncertainty, just like startups. But, as any startup can tell you, this opens up a tremendous set of opportunities for the rest of us. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. Is that a lot? Is that good?
All I see is a name, an icon, a price, the developers name, and a review star-rating. The reviews are all over the map. But even clicking through to see a screenshot and some reviews is incredibly time consuming, given the hundreds of apps in most categories. No departments The Five Whys for Startups (for Harvard Business R.
Thanks to those of you who were willing to fill out the survey, I learned my net promoter score (about 25) as well as some clear other segmentation insights: about 80% of you are founders of or work at a startup, you read many of the same other blogs, and many of you would like to engage with Lessons Learned in formats and venues beyond this blog.
My code base can be changed or refactored to support major changes to the feature. Come hear me speak at the Startup Lessons Learned conference in San Francisco on April 23rd. Use the code “LAURAK&# for 20% off your ticket price! Do I Have the Time and Willingness to Support and Improve this Feature Going Forward?
The credit is due to much smarter people than me, and to the incredible power of necessity, that mother of invention. You may have to staff up a large customer service department to review and approve all of the items. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Heres what I mean.
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. And yet I keep returning to PHP as a development platform, as have most of my fellow startup CTOs. Memory-resident code made it slightly slower to iterate on scripts.
Bring in an expert CEO with outstanding business credentials and startup experience to focus on relentless execution. I had the privilege, and the misfortune, to be involved with a startup that executed this plan flawlessly. I know of at least five former employees that went on to become startup founders. Focus on quality.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content