Trending Sources

Tesla and Adobe: Why Continuous Deployment May Mean Continuous Customer Disappointment

Steve Blank

In the last few years Agile and “Continuous Deployment” has replaced Waterfall and transformed how companies big and small build products.

Why Continuous Deployment?

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? 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. Nice post.

Continuous deployment for mission-critical applications

Startup Lessons Learned

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. Another release?

Case Study: Continuous deployment makes releases non-events

Startup Lessons Learned

Without being able transparently modify the software in situ, is it still possible to deploy on a continuous basis? Read on to find out.

Tesla and Adobe: Why Continuous Deployment May Disappoint Customers

Fresh Inc.: The Staff Blog

In the last few years agile and "continuous deployment" have replaced waterfall and transformed how companies big and small build products.

Tracking Every Release

Code as Craft

Change to application code (deploys) are opportunities for failure. To track time-based events, the value sent for the metric can simply be “1″ Erik Kastner added this right into our code deployment tool so that every single deploy is automatically tracked. Something obviously happened here… but what was it? Ah-ha!

PHP 17

Continuous deployment with downloads

Startup Lessons Learned

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. Thanks for the comments.

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

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. This engineering manager is a smart guy, and very experienced. Sound good? Heres why.

We Invite Everyone at Etsy to Do an Engineering Rotation: Here’s why

Code as Craft

At Etsy, it’s not just engineers who write and deploy code – our designers and product managers regularly do too. Whoa.”.

From Alpha to Beta: Continuous Deployment at Threadflip

Launching Tech Ventures

by Samantha Lynch & Elizabeth Trongone Having prior product management experience in companies like Birchbox, Warby Parker and Group Commerce, we sought to continue to hone our product management skills through the lens of Launching Technology Ventures. Certain critical pain points and areas of confusion came up continuously.

Engineering Social Commerce

Code as Craft

In this post we explore some of the engineering challenges we faced in building a social commerce feature like the gift recommender. At Etsy, we build our system in a continuously deployed environment which allows us to quickly iterate and experiment. The gift recommender is social in that it brings your friends to Etsy.

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

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. Its a nice complement on the product engineering side to his customer development methodology. for H.

Optimizing for developer happiness

Code as Craft

In the talk, I go into the philosophical reasons why continuous deployment makes engineers happy, how radically decentralizing authority and thinking of your team as a community optimize for happiness, and the how our approach to tooling makes everything work. engineering philosophy video

API First Transformation at Etsy – Operations

Code as Craft

Continuing down this path we would have exhausted space and power in our datacenters. Operations: Architecture Implications. We had a problem.

API 16

API First Transformation at Etsy – Concurrency

Code as Craft

Before we deploy code to Etsy.com, we check if the compiled routes and client code are up to date via Jenkins. Finally, how did it end?

API 19

The Product Hacking Ecosystem

Code as Craft

Continuous deployment, the practice of pushing your code live the moment its ready, is absolutely essential for product hackers.

Moving Fast at Scale: a microconference at SXSW

Code as Craft

We also deployed the site to production 517 times with changes from over 70 unique individuals. We’ve written about how we do it here on Etsy’s engineering blog (look here , here , and here for a sampling) but we’ve never explained it all in one place, in person, with free beer. engineering operations philosophy

Chad 11

Lessons Learned: SEM on five dollars a day

Startup Lessons Learned

Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. You declare how much someone clicking an advertisement is worth to you, and then the search engine does its best to get you as many clicks as it can at that price. Labels: search engine marketing 4comments: Tauya said.

SEM 20

Static Analysis for PHP

Code as Craft

They form an important part of our continuous deployment pipeline along with one-button deploys, fast unit and functional tests, copious amounts of graphing, and a fantastic development environment to make sure code flows safely and securely to production. engineering infrastructure securitySanity and Style Checking.

PHP 15

Hands-on Lessons for Advanced Topics in Entrepreneurship

Startup Lessons Learned

We wanted to give you a rundown of what’s in store, along with particular insight into two of the workshops we’re most excited to have lined up for Gold and VIP attendee s—one session with Jez Humble on implementing continuous delivery and one with Alistair Croll on Lean analytics for corporate entrepreneurs. How do you address that?

Lean 23

Lessons Learned: Five Whys

Startup Lessons Learned

By continuously adjusting, we eventually build up a robust series of defenses that prevent problems from happening. Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day. Heres how it works. Dont over-invest.

Four myths about the Lean Startup

Startup Lessons Learned

And they can benefit from the speed and discipline of starting with a minimum viable product and then learning and iterating continuously.

Lean 43

Translation Memory

Code as Craft

Since we are a company with a continuous deployment development process, we do this on a daily basis and as an result get a significant number of new messages to be translated along with changes or deletions of existing ones that have already been translated. data engineering internationalizationBy: Diego Alonso. 80% Join now.

Do lean startup principles have a place in the enterprise?

The Next Web

Lean startup engineering. Lean startup engineering seems to work for consumer products. Real world example: WebVan vs Zappos. Absolutely.

Lean 25

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

Finding great engineers is hard; figuring out whos good is even harder. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. have found this quite rare in engineers. Many of us engineers are strong introverts, without fantastic people skills. Brains. Communication. Drive.

Infrastructure upgrades with Chef

Code as Craft

In addition to our production infrastructure, every engineer and designer also have their own VM to develop on the Etsy stack (see this post for details). We have about 30 engineers regularly making changes to our cookbooks. For infrastructure changes we have the same continuous deployment mentality. We have two. So if.

Lessons Learned: Work in small batches

Startup Lessons Learned

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Every time an engineer checks in code, they are batching up a certain amount of work. Normally I focus on the techniques you need to reduce batch size, like continuous integration.

The Lean Entrepreneur is here

Startup Lessons Learned

My personal background was as an engineer and my companies had been Web-based startups, so that is what I wrote about. It's a big tent.

Lean 60

Fear is the mind-killer

Startup Lessons Learned

spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place. was a common refrain.

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

So I initially gravitated to the CTO title, and not VP of Engineering. And what about if deployment takes forever? Should you take them?

CTO 61

The Awesomeness of a Hackathon

Feld Thoughts

Some release weekly, or even daily. I’ve become a big advocate of true Agile development (partly because of my experience with Rally Software – the leader in Agile software development environments) and – more recently – the notion of trying to get to continuous deployment which has been popularized by Eric Ries. Form teams.

Wiki 32

Lessons Learned: The lean startup

Startup Lessons Learned

See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. Since that time we've seen a massive change from product engineering to financial engineering. September 11, 2008 2:06 PM Editor said.

Lean 47

Lean Startup at Scale

Startup Lessons Learned

That is, once you’re no longer a small company and you have some success, how do you execute and continue to grow through innovation? We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. Week 1 - New Feature 2 - Development and testing continue together.

Lean 40

Lessons Learned: The three drivers of growth for your business.

Startup Lessons Learned

break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Thats why eBay advertises on search engines, and Facebook doesnt. Labels: search engine marketing 0comments: New comments are not allowed. Choose one. This has led to exponential growth.

Minimum Viable Product: a guide

Startup Lessons Learned

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Its power is matched only by the amount of confusion that it causes, because its actually quite hard to do. But I wanted to say a few words first.

Pivot, don't jump to a new vision

Startup Lessons Learned

As the CTO/VP Engineering, I was the worst offender. That means that I (and other engineers) were able to participate in the problem team discussions. Such discussions would have been impossible in our execution-oriented engineering team meetings. Case Study: Continuous deployment makes releases n. It was painful.

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

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 continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Youd better. Expo SF (May.

Lean 33

Moving Fast at Scale: the slides, and a reprise in NYC

Code as Craft

Continuous Deployment: The Why and the How (Kellan Elliott-McCrea, VP of Engineering). Links to our slides from Austin are below.

Chad 15

Teaching Testing: Our Testing 101 Materials

Code as Craft

Etsy engineers have a wide variety of backgrounds, strengths, and weaknesses, so there are no engineering skills we can take for granted. And there are things you can’t just assume engineers will learn for themselves because you throw a codebase and a workflow at them. Both use PHP and PHPUnit.

PHP 5

Lessons Learned: Venture Hacks interview: "What is the minimum.

Startup Lessons Learned

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Part one is up on their site today , in text, audio and slide format. To hear full audio and a complete transcript, click through to Venture Hacks.