BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Articles

  • Practical Postmortems at Etsy

    We take a look at Etsy's blameless postmortems, both in terms of philosophy, process and practical measures/guidance to avoid blame and better prepare for the next outage. Because failures are inevitable in complex socio-technical systems, it’s the failure handling and resolution that can be improved by learning from postmortems.

  • Conversation Patterns for Software Professionals - Part 4

    In the fourth article in the Conversation Patterns for Software Professionals series Michał Bartyzel focuses on asking the right questions.

  • Q&A with Jez Humble, Joanne Molesky and Barry O’Reilly on Lean Enterprise

    The "Lean Enterprise" book authors discuss how traditional management practices fail to balance innovation and product exploitation as they require very different sets of capabilities.

  • An Experiment: The GROWS™ Method

    Agile software development is in a rut. The most popular agile methods are consistently mis-applied, mis-understood, mis-used, and all too often abandoned by the companies who need them the most. But worse than that, our popular agile methods are not actually agile themselves! This article proposes a new approach that recognizes and works around limitations in human cognition and decision making

  • Version Control, Git, and your Enterprise

    This article is about understanding Git – both its benefits and limits – and deciding if it’s right for your enterprise. It is intended to highlight some of the key advantages and disadvantages typically experienced by enterprises and presents the key questions to be contemplated by your enterprise in determining whether Git is right for you and what you need to consider in moving to Git.

  • What is Success for a Scrum Master?

    Experienced Scrum Masters explain how they define and measure their own personal success as Scrum Masters, and share their lessons learned about how to achieve success. From dealing with stakeholders, to how to improve coaching skills and how to help the team achieve a sustainable pace, the lessons come from many years of experience and will help you improve your performance as a Scrum Master.

  • Book Review and Q&A - The Art of Scalability

    The Art of Scalability is a book on scaling organisations to adapt to web scale growth of their products and services. As well as having technical and architectural implications, scale needs to be dealt with on the organizational level. The goal is to show the reader how to organize technology, people and processes to result in a virtuous circle, a path of continuous improvement to scalability.

  • Author Q&A on Leading without Authority

    Tathagat Varma, shares his experience of working as an individual contributor at a deeper leadership level. He refers to this as an "Individual Leader". This post explains how to lead without authority.

  • Refactoring for Software Design Smells Review and Q&A with the Authors

    Refactoring for Software Design Smells by Girish Suryanarayana, Ganesh Samarthyam, and Tushar Sharma presents a catalogue of typical software design smells and how they can be fixed.

  • Agile Coaching - Lessons from the Trenches

    High performing teams do not often happen organically; they are a return on investment. In this article, we will use our hard fought experience from the trenches to shed light onto Agile Coaching. First, defining what being an Agile Coach means, what skills and competencies are necessary to be successful. Then, examining patterns and anti-patterns for both in-house coaches and coach-consultants.

  • The Design and Implementation of the FreeBSD Operating System, Review and Q&A with Authors

    The Design and Implementation of the FreeBSD Operating System is a long awaited update to a successful and authorative guide to the FreeBSD kernel. The second edition covers all major improvements between FreeBSD version 5 and 11 and, according to the publisher, it has been extensively rewritten for one-third of its content, while another one-third is completely new.

  • Limitations of Technical Debt Quantification: Do you Rely on these Numbers?

    Technical debt quantification tools attempt to quantify the existing technical debt in a software product. However, the present set of quantification tools suffers from various limitations such as limited or no support for quantification of all technical debt dimensions, generalized absolutization, and missing interest component. Hence, quantified cost and effort must be interpreted with caution.

BT