Waza keynote: Idea to Delivery

Idea to Delivery app development in 2012 Adam Wiggins Waza, January 2012Friday, January 13, 2012

Friday, January 13, 2012

TechniqueFriday, January 13, 2012

Small sharp toolsFriday, January 13, 2012

Richard Feynman Murray Gell-MannFriday, January 13, 2012

“ The Feynman Problem-Solving Algorithm:Friday, January 13, 2012

“ The Feynman Problem-Solving Algorithm: (1) Write down the problem.Friday, January 13, 2012

“ The Feynman Problem-Solving Algorithm: (1) Write down the problem. (2) Think very hard.Friday, January 13, 2012

“ The Feynman Problem-Solving Algorithm: (1) Write down the problem. (2) Think very hard. ” (3) Write down the answer. - Murray Gell-Mann http://quotations.tastefulwords.com/murray-gell-mann/the-feynman-problem-solving-algorithm/Friday, January 13, 2012

Where can we look for new techniques?Friday, January 13, 2012

Zoom outFriday, January 13, 2012

Idea to deliveryFriday, January 13, 2012

Idea Implementation Deployment DeliveryFriday, January 13, 2012

Programmer Idea Implementation Deployment DeliveryFriday, January 13, 2012

programmer vs app developerFriday, January 13, 2012

Breadth of responsibilityFriday, January 13, 2012

Programmer Idea Implementation Deployment DeliveryFriday, January 13, 2012

App developer Idea Implementation Deployment DeliveryFriday, January 13, 2012

4 techniques from the last decade 6 techniques of the emerging futureFriday, January 13, 2012

4 techniques from 2000 - 2010Friday, January 13, 2012

1. AgileFriday, January 13, 2012

1. Agile 2. Software-as-a-serviceFriday, January 13, 2012

1. Agile 2. Software-as-a-service 3. Web frameworksFriday, January 13, 2012

1. Agile 2. Software-as-a-service 3. FrameworksFriday, January 13, 2012

1. Agile 2. Software-as-a-service 3. Frameworks 4. VirtualizationFriday, January 13, 2012

1. Agile 2. Software-as-a-service 3. Frameworks 4. Virtualization CloudFriday, January 13, 2012

1. Agile 2. Software-as-a-service 3. Frameworks 4. CloudFriday, January 13, 2012

Agile Framework Cloud SaaS Idea Implementation Deployment DeliveryFriday, January 13, 2012

Scrum Rails Heroku URL Idea Implementation Deployment DeliveryFriday, January 13, 2012

Agile + Frameworks + Cloud + SaaSFriday, January 13, 2012

The 2010s way for app developmentFriday, January 13, 2012

6 techniques for 2012 and beyondFriday, January 13, 2012

Technique 1Friday, January 13, 2012

Technique 1 Deploy from day 1Friday, January 13, 2012

Early development Idea Implementation Deployment DeliveryFriday, January 13, 2012

http://ruby.railstutorial.org/ruby-on-rails-tutorial-bookFriday, January 13, 2012

“ Even at this early stage, we’re already going to deploy our (still- empty) Rails application to production. This step is optional, but deploying early and often allows us to catch any deployment problems early in our development cycle.Friday, January 13, 2012

The alternative—deploying only after laborious effort sealed away in a development environment— often leads to terrible integration headaches when launch time comes.Friday, January 13, 2012

Technique 1 Deploy from day 1Friday, January 13, 2012

Technique 2 Continuous deploymentFriday, January 13, 2012

Deploy schedulesFriday, January 13, 2012

Deploy on demandFriday, January 13, 2012

Is continous deployment real?Friday, January 13, 2012

1.1 million deploys to Heroku in the last monthFriday, January 13, 2012

Technique 2 Continuous deploymentFriday, January 13, 2012

Technique 3 Feature flagsFriday, January 13, 2012

http://code.flickr.com/blog/2009/12/02/flipping-out/Friday, January 13, 2012

Decouple these Idea Implementation Deployment DeliveryFriday, January 13, 2012

Deployed, but inactiveFriday, January 13, 2012

Still the active path for all usersFriday, January 13, 2012

Activated for some usersFriday, January 13, 2012

Activated for all usersFriday, January 13, 2012

Dead code, now safe to removeFriday, January 13, 2012

A gradual & granular method for deliveryFriday, January 13, 2012

Technique 3 Feature flagsFriday, January 13, 2012

{sidebar}Friday, January 13, 2012

We see friction across 1000s of appsFriday, January 13, 2012

TrendsFriday, January 13, 2012

PrinciplesFriday, January 13, 2012

http://www.12factor.net/Friday, January 13, 2012

{continue!}Friday, January 13, 2012

Technique 4 Dev/prod parityFriday, January 13, 2012

Development: SQLite Production: PostgreSQLFriday, January 13, 2012

Development: SQLite Uh oh. Production: PostgreSQLFriday, January 13, 2012

Development and production as similar as possibleFriday, January 13, 2012

http://www.12factor.net/dev-prod-parityFriday, January 13, 2012

Can we go further?Friday, January 13, 2012

Virtual machinesFriday, January 13, 2012

http://railscasts.com/episodes/292-virtual-machines- with-vagrant?view=asciicast http://unfoldthat.com/2011/05/06/using-vagrant-for- your-django-development.html http://walkah.net/blog/why-vagrantFriday, January 13, 2012

Technique 4 Dev/prod parityFriday, January 13, 2012

Technique 5 Stay close to productionFriday, January 13, 2012

Developers do deploysFriday, January 13, 2012

Helmuth von Moltke the ElderFriday, January 13, 2012

“ No battle plan survives first contact with the enemy.Friday, January 13, 2012 - von Moltke ”

“ No code survives contact with production load.Friday, January 13, 2012 ”

Your code in development is theoreticalFriday, January 13, 2012

Your code in production is realityFriday, January 13, 2012

“ Everyone has a plan till they get punched in the mouth.Friday, January 13, 2012 - Mike Tyson ”

Real user behavior will punch you in the mouthFriday, January 13, 2012

Sword-in-the-bag bugFriday, January 13, 2012

Searching for the answer in my codeFriday, January 13, 2012

Found the answer by observing productionFriday, January 13, 2012

Technique 5 Stay close to productionFriday, January 13, 2012

Technique 6 Logs as event streamsFriday, January 13, 2012

The pulse of your applicationFriday, January 13, 2012

http://www.12factor.net/logsFriday, January 13, 2012

Everything that your app is doing, right nowFriday, January 13, 2012

Everything that your app has done, in the pastFriday, January 13, 2012

Log archival & search toolsFriday, January 13, 2012

Papertrail http://addons.heroku.com/papertrailFriday, January 13, 2012

Loggly http://addons.heroku.com/logglyFriday, January 13, 2012

Ivory-tower thinkingFriday, January 13, 2012

More evidence, less speculationFriday, January 13, 2012

The evidence is in your logsFriday, January 13, 2012

Technique 6 Logs as event streamsFriday, January 13, 2012

RecapFriday, January 13, 2012

Deploy from day 1 early and often avoids launch-day headachesFriday, January 13, 2012

Continuous deployment deploy on days 2, 3, and nFriday, January 13, 2012

Feature flags decouple deployment & deliveryFriday, January 13, 2012

Dev/prod parity avoid those little incompatibilitiesFriday, January 13, 2012

Stay close to production reality is production load and real user behaviorFriday, January 13, 2012

Logs as event streams an evidence-based approachFriday, January 13, 2012

Call to actionFriday, January 13, 2012

? Are you a programmer or an app developerFriday, January 13, 2012

Come out of our programmer caveFriday, January 13, 2012

Connect with our code in the wildFriday, January 13, 2012

Connect with our usersFriday, January 13, 2012

Take responsibility for idea to delivery Idea DeliveryFriday, January 13, 2012

Fin. Adam Wiggins @hirodusk http://adam.heroku.com/Friday, January 13, 2012

http://a0.twimg.com	15
https://twitter.com	1
http://us-w1.rockmelt.com	1

Waza keynote: Idea to Delivery

by Adam Wiggins on Jan 13, 2012

Accessibility

Categories

Tags

Upload Details

Usage Rights

3 Embeds 17

Statistics

Waza keynote: Idea to Delivery — Presentation Transcript