Kolton Andrus is working as "chaos engineer" at Netflix which means he is getting paid for breaking things in production. We are talking with about how to improve overall system quality by injecting failures in production systems, about the idea of "anti-fragility" in the context of software and about how engineering teams of all layers can benefit from a failure injection infrastructure.
Elisabeth Hendrickson discusses her move from consulting to take on the role of Director of Quality Engineering for Pivotal Labs, how important engineering technical practices are to building quality in from the ground up and how scaling agile across many teams requires a structure that supports self-organization within organizational constraints.
Emma shares her view on Systems Thinking and why is it important in modern organizations that want to learn and move forward. She also delves into other topics from her experience such as working in the Middle East, women and technology and work-private life balance as a working mother.
Crista Lopes discusses the idea of using constraints to define styles of programming and architecture. Also: large scale static analysis of open source code, Open Simulator and VR, and much more.
Brandon Carlson discusses his Agile journey, measurement and some code metrics tools he is working on. He also shares his views on professionalism and the importance of not fearing your customers.
Brian Foote looks back at the promises of OOP and discusses which, if any, of them became reality. Also: a look at NoSQL, refactoring and code quality, testing and static typing and more.
In this interview, Joshua Kerievsky, founder of Industrial Logic, discusses the need for developer performance metrics to enable organizations to determine the capabilities of developers. He also discusses his project known as the Limited Red Society. The goal of the Limited Red Society is to help developers limit the amount of time their code is in the red.
In this interview filmed during RubyFringe 2008, Luke Francl explains his position towards testing. While supporting unit testing, he thinks testing is not going to reveal all application defects. Development teams should also practice code reviews and usability tests which are likely to discover bugs not visible though other methods.
Debate sprang up at JAOO '07 around Bob Martin's assertion that "nowadays it is irresponsible for a developer to ship a line of code he has not executed in a unit test." In this InfoQ video, he debated with Jim Coplien on this and other topics, including Design by Contract vs. TDD and how much up-front architecture is needed to keep a system consistent with the business domain model.
Ron Jeffries' upcoming book looks at how tracking "Running Tested Features" is the essential element of Agility, from which all other practices and activities necessarily follow. Deborah Hartmann interviews Ron who takes to the whiteboard to explain how, when supported by XP's "simple design" practice, RTF helps teams deliver consistently without building up costly technical debt.