BT

InfoQ Homepage Pair Programming Content on InfoQ

  • Adopting Continuous Delivery at teamplay, Siemens Healthineers

    Continuous Delivery is about working in a way that keeps the system in a releasable state throughout its development. This article describes how a large software development organization at Siemens Healthineers started the transformation towards Continuous Delivery. It describes the strategy and tactics used to gradually and safely change the development process in a regulated medical domain.

  • Refactoring to a Deeper Model

    Paul Rayner uses a case study to demonstrate how refactoring your code can lead to a deeper understanding of your domain model. Through common code refactorings, combined with the implementation of patterns, the codebase became more cohesive and easier to reason about, reducing the time to perform some common tasks from weeks or months to just hours.

  • Coaching Technical Practices

    In the past 4-5 years I have been working as a software development coach, helping organizations around London improve their technical practices. I focus on XP practices, specifically TDD, Pair Programming, Refactoring and Simple Design. In this article I share my experiences organizing coaching sessions, including subject selection and sequencing, exercises for each subject and session formats.

  • Escaping Method Prison

    Methods are our best tool to get great software. But today they put us in method prisons with method wars, reliance on gurus and swings from method to method. How foolish is this? It needs to be stopped. The new Essence standard efficiently stops that path. And, teams get better methods, selected from a practice library and support in their daily work. Executives get forever learning org’s.

  • 2017 State of Testing Report

    The State of Testing 2017 report provides insights into the adoption of test techniques, practices, and test automation, and the challenges that testers are facing. This is fourth time that this survey has been done. InfoQ held an interview with the organizers of the State of Testing survey.

  • Technical Practices as a Hack on Consciousness: Why to Hack Yourself

    Software technical practices are usually adopted as a means of creating better products. These practices can create and maintain a healthy human system. Technical practices raise the consciousness of individuals and the team as a whole. Technical practices hack consciousness giving us a quick, deep chute into depths of connection that improve our selves, our products, and our world.

  • Pair Programming Is No Panacea

    Is pair programming all that it's cracked up to be? Contrary to popular belief, pairing can lead to a decrease in creativity, groupthink, inappropriate feedback, and can be demoralizing. Wes Higbee explores why it definitely shouldn't be mandated, and why you should consider other options where it could be beneficial.

  • Why Won’t They Pair?

    Pair programming is one of the core techniques of eXtreme Programming and has been shown to be effective for knowledge sharing as well as code quality, but it is a practice that is often not used, even in the most agile of organizations. Linda Cook explores why that is and provides some advice on how to encourage teams to try the practice.

  • The Way to No-Hotfix Deployment

    Hot-fix redeployment is a waste of time and effort at best, and often a source of further regression, Adam discusses some ready-to-use techniques that helped he and his team reduce the frequency of hot-fix deployments to almost zero.

  • Why We Fail to Change: Understanding Practices, Principles, and Values Is a Solution

    There’s no reward for being a Scrum or kanban shop if we are not delivering value to customers. We see virtually no impact of agile or lean on the bottom line of success rates of improvement initiatives, because organizations often look for recipes. We need to change our mindset, and focus on the principles that people follow and values they share and the bigger whole: organizational culture.

  • Q&A with Sandro Mancuso about The Software Craftsman

    In the book The Software Craftsman, Professionalism, Pragmatism, Pride Sandro Mancuso explores how craftmanship plays a role in agile software development. The book contains stories, examples and practical advice for software developers and other professionals involved in software projects to achieve technical excellence and customer satisfaction.

  • Revisiting XP: be a thoughtful programmer by exercising more collective ownership

    Frequently developers cause and face regular frustration often due to a lack of consideration for those who come after them. This article explores the approach of programming more thoughtfully by revisiting one of the most simple (yet often misunderstood) XP rules: collective ownership

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.