Todd Charron talks about some of the outcomes from Lean Startup Machine in Toronto, applying Lean Startup in the Enterprise and how can us improvisation techniques in Agile to reduce our fears.
Chris McMahon discusses radically open source testing at Wikipedia and has put out a call for the testing community to participate, as well as discussing approaches to browser test automation.
Bryan Beecham (aka Billy Garnet) reminds us that "XP not dead!" and shares his approach to teaching TDD and refactoring with Lego and applying XP and craftsmanship in teams as well as the human body.
Dave Farley discusses the reasons for Continuous Delivery and Continuous Deployment, the advantages and challenges they pose, and much more.
Rachel Laycock explains her experience with bringing Continuous Delivery to companies, the main technical and social obstacles, and much more.
Alex Papadimoulis shares his thoughts on distribution vs delivery, decoupling infrastructure (pull) from application (push) deployments and keeping delivery systems simple, especially for web scale applications. In particular Alex describes three different types of roll-outs: Live, Rolling and Parallel and their applicability (cloud-based delivery vs in-house servers).
In this InfoQ interview, Michael Nygard explores some of the available loopholes in the CAP theorem helping architects to engineer distributed systems that meet their needs. He also discusses new patterns he’s observed since his book, Realease IT and shares his thoughts on continuous delivery, DevOps and ALM.
IT thought leader Jeff Sussna answers a range of questions about operational efficiency and cloud trends. He discusses new thinking around production freezes and adopting continuous delivery. Sussna explains how companies should understand the entire lifecyle of a customer’s cloud experience. Finally, he shares insight into AWS and their leading position in the cloud.
In this interview we talk with Adrian Cockcroft, the architect for Netflix’s cloud systems team. We discuss how Netflix combines 300 loosely coupled services across 10,000 machines. An interesting revelation is that they fully embrace continuous delivery and each team is allowed to deploy new versions of their service whenever they want.
More than a year since his book Contiuous Delivery came out, author Jez Humble talks about changes in CD, and its relationships with Cloud development, ALM. He also shares his Four Principles Of Low-Risk Software Releases. Other topics include TDD, feedback at different stages of the pipeline, and his involvement with Devops.
Peter Bell discusses the state of Java today and whether startups are using it or not, polyglot programming, startups in New York, how to keep up to date with technology, and much more.
Based onconcepts presented in his book, Scott Ambler describes Disciplined Agile Delivery (DAD) as a hybrid approach that extends Scrum, Agile modeling, Unified Process. DAD is a people-first process that's goals-based rather than prescriptive, addresses the entire lifecycle and shares many concepts presented in continuous delivery. Scott also discusses the DevOps movement and how DAD addresses it