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
Amsterdam-based Rockstart Accelerator , one of the many, many startup accelerators in Europe, is taking the first class of startups who’ve graduated from its six-month program stateside this month. Wercker : a continuousdeployment solution for software developers, hosted in the cloud.
Eric) In a bar in Amsterdam in 2005, my two cofounders and I came to the sad conclusion that startup we tried to built for two years was doomed. My co-founders decided startup life wasn't for them. We connected the sensors to a seven year old pc with an Arduino-like interface that ran a simple drum program we developed.
This post was written by Sarah Milstein, co-host of The Lean Startup Conference. Often, in very young organizations, those people are simply the founders. Last year, the co -founders of B ack to the Roots talked about their innovation accounting and how they were ignoring sales metrics in order to grow. Glad you asked.
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 Monday, January 18, 2010 Case Study: Continuousdeployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuousdeployment. ContinuousDeployment is Continuous Flow applied to software.
Lessons Learned by Eric Ries Monday, December 28, 2009 Continuousdeployment for mission-critical applications Having evangelized the concept of continuousdeployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it.
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. At IMVU it’s a core part of our culture to ship.
This post was co-written by Sarah Milstein & Eric Ries, co-hosts of The Lean Startup Conference. We’ve just published the program for this year’s Lean Startup Conference , December 9 to 11 in San Francisco, and we can say without hesitation that it’s completely unlike any other entrepreneurship conference in existence.
Lessons Learned by Eric Ries Sunday, February 22, 2009 Please teach kids programming, Mr. President Of course, what I really mean is: let them teach themselves. 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?
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. Thanks for the comments.
I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible.
He previously co-founded and served as Chief Technology Officer of IMVU. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. October 13, 2008 6:47 PM Luke G said. Eric, love the blog.
We had a great on-boarding process, complete with a mentoring program and a syllabus of key ideas to be covered. We didnt start with a great program like that, nor did we spend a lot of time all at once investing in it. It seems your cluster architecture is one of the key architectural constraints making continuousdeployment possible.
Its had tremendous impact in many areas: continuousdeployment , just-in-time scalability , and even search engine marketing , to name a few. When operating with continuousdeployment, its almost impossible to have integration conflicts. Case Study: Continuousdeployment makes releases n.
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.
If you havent seen it, Pascals recent presentation on continuousdeployment is a must-see; slides are here. Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. If you havent seen it, Pascals recent presentation on continuousdeployment is a must-see; slides are here.
Some startups fail because the founders cant have this conversation - they either blow up when they try, or they fail to change because they are afraid of conflict. Although I wish I could take credit for these pivots, the reality is that they were not caused by my singular insight or that of my other co-founders.
To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuousdeployment. The Extreme Programming folks call those "spikes", and generally don't check them in.) One last thought.
If done right, a programming interview serves two purposes simultaneously. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. My technique is to structure a technical interview around an in-depth programming and problem-solving exercise. Have you tried it?
Instead, we do everything possible to validate the founders belief. Most people cant sustain more than a few of these iterations, and the founders rarely get to be involved in the later tries. In order to do this, we have our customer development team work hard to find a market, any market, for the product as currently specified.
I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal. Its easier to believe in a glorious future when you have only zeroes, for everyone: founders, investors, and employees. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal.
These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. I pick that example on purpose, for two reasons: 1) most of the companies I work with deal with this problem and yet 2) almost none of them have any kind of training program in place for new employees.
It was actually my co-founder Will Harvey who taught me to present this data in the simple format weve discussed in this post. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.
When I was working my first programming jobs, I was introduced to the following maxim: "time, quality, money - pick two." When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. Case Study: Continuousdeployment makes releases n.
But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuousdeployment, youd better be able to certify that build too, which brings us to. For more on continuousdeployment, see Just-in-time Scalability. Can you make a build in one step?
I also owe a great debt to Kent Beck, whose Extreme Programming Explained: Embrace Change was my first introduction to this kind of thinking. (So Mark Montgomery Founder Kyield Initium VC September 12, 2009 4:21 AM Mark Montgomery said. Case Study: Continuousdeployment makes releases n. Otherwise it's a great idea.
So what does CTO mean, besides just "technical founder who really cant manage anyone?" ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuousdeployment makes releases n.
They are leaders, visionaries, founders and managers having tremendous success. They are leaders, visionaries, founders and managers having tremendous success. Case Study: Continuousdeployment makes releases n. Yet talent organized improperly can lead to failure. I was an engineer on the engineering team.
For startups that are tempted to mimic this behavior, I suggest reading the great account of the early Apple in Founders at Work.) ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.
► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuousdeployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.
Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Once the different parts of the team can trust each other again, well have the basis we need to start a true continuous improvement feedback loop. Case Study: Continuousdeployment makes releases n.
► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuousdeployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.
For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. I assumed he was there to refute my critique of extreme programming, but nothing could be further from the truth. Was that really the Kent Beck?
If we’re practicing continuousdeployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems. Case Study: Continuousdeployment makes releases n. We can also ask: how would we fix the problem if it does occur?
Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Case Study: Continuousdeployment makes releases n. for Harvard Business Revie.
► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuousdeployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.
It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. These founders have not managed, to borrow a phrase from Steve Blank , to create a scalable and repeatable sales process. More on that in a moment. They are close to breakeven.
► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuousdeployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.
► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuousdeployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.
Weve got a new scholarship program up and running. Weve gone from total obscurity to something people are beginning to misunderstand and even co-opt. Doesnt the communication overhead of a large team lead to chaos of overlapping experiments and continuously-deployed bugs?" "If Weve got a new scholarship program up and running.
sachinrekhi : "Visionary customers are as smart if not smarter then the founders" #leanstartup Theres no skipping the chasm. My cofounders and I would hash out nuances and details almost every day, re-drawing diagram after diagram on the whiteboard. Case Study: Continuousdeployment makes releases n.
Founders push for it. In some ways, founders are even worse. My experience is that many founders actually have a deep anxiety that maybe they are not succeeding. Case Study: Continuousdeployment makes releases n. See if their answer is about tactics or strategy. Who doesnt want to see their name in print?
I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. Case Study: Continuousdeployment makes releases n.
Lessons Learned by Eric Ries Friday, July 9, 2010 Founder personalities and the “first-class man&# theory of management At any given time, something like four percent of the US population is engaged in some form of new-company-creation. Are we solving the right problem? We can do better by focusing on process instead of personality.
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