BT

Facilitating the spread of knowledge and innovation in professional software development

Contribute

Topics

Choose your language

InfoQ Homepage Defects Content on InfoQ

Articles

RSS Feed
  • Continuous Learning as a Tool for Adaptation

    The fifth and capstone article in a series on how software companies adapted and continue to adapt to enhance their resilience explores key themes with a special view on the practicality of organizational resilience. It also provides practical guidance to engineering leadership and recommendations on how to create this investment.

  • Exploring Costs of Coordination During Outages - QCon London Q&A

    Coordinating different skills, knowledge and experience is necessary for coping with complex, time-pressured events, but it incurs costs. Well-designed coordination is smooth and can be trained for. Learning how to take initiative, being observable to your counterparts and engaging in reciprocity are examples of strategies engineers can use to lower costs of coordination during outages.

  • The Ultimate Feedback Loop: Learning from Customer Reported Defects

    Investigating the root causes of customer reported defects will have a great impact on your organization. The best ways to ensure customer satisfaction, lower costs and increase employee engagement is to look inside — you already have the data. At the end, it’s all about continuous improvement.

  • Q&A with Diomidis Spinellis on Effective Debugging

    The book Effective Debugging by Diomidis Spinellis describes 66 different approaches for effective debugging of applications and systems. It provides methods, strategies, techniques, and tools for finding and removing faults, and gives examples for using them in different settings.

  • Now or Never: the Ultimate Strategy for Handling Defects

    How do you handle a long list of defects in your project? You don't. If it is not worth fixing a defect right now, it’s not likely that we will find the time to do it later. Also, it becomes more and more difficult over time to correct the defect, so it is cheaper to solve it now. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them.

  • Q&A about the book Common System and Software Testing Pitfalls

    The book Common System and Software Testing Pitfalls by Donald Firesmith provides descriptions of 92 pitfalls that make testing less efficient and effective. The descriptions explain what testers and stakeholders can do to avoid falling into the pitfalls and how to deal with the consequences when they have fallen into them.

BT