BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Code Quality Content on InfoQ

  • Q&A on The Agile Developer's Handbook

    The book The Agile Developer’s Handbook by Paul Flewelling provides the fundamentals of agile and explores intermediate and advanced topics like metrics for delivery, technical practices, delivering value, team dynamics, building quality in, and becoming an agile organization.

  • Q&A on the Book What Drives Quality

    Quality is a critical aspect of all software products, irrespective of the domain the product is used in and what approach is taken to building it. Ben Linders has released a new book titled "What Drives Quality" in which he provides concrete examples and actionable advice to help identify and improve the quality of software products.

  • Q&A on The Digital Quality Handbook

    The Digital Quality Handbook explores the challenges of testing mobile and web applications and shows how to apply agile practices to deliver quality at speed. Some of the topics covered are test automation, sizing mobile testlabs, addressing test flakiness, crowdsourced testing, performance testing, and applying DevOps practices.

  • Are Unit Tests Part of Your Team’s Performance Reviews?

    No matter how often you conduct performance reviews, there is no doubt unit testing should be one of the metrics measured. Eli Lopian explains what makes a good unit test and how to measure them to ensure your development team is truly agile.

  • Agile Sailors - A Journey from a Monolithic Approach to Microservices

    Over the last couple of years eSailors IT solutions has implemented big technological and organisational changes: from functional silos to cross-functional teams, from a work flow that looked like an assembly line to dynamic loops, from a monolithic platform to microservices, from hierarchical command-and-control to leadership as a team sport. This article provides a summary of their journey.

  • 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.

  • 0 Bugs Policy

    Gal Zellermayer describes the 0 bugs policy, a process for handling bugs that is based upon 1 rule: whenever you encounter a new bug, you should either fix that bug, or close it as "won't fix" and don't think about it again.

  • 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.

  • Q&A on The Agile Mind-Set

    Gil Broza explores agile values, beliefs and principles, and explains how they can be used to drive agile adoption in his book The Agile Mind-set. The book provides ideas, examples, and anecdotes that organizations can use to make a shift to agile.

  • Q&A on Test Driven Development and Code Smells with James Grenning

    InfoQ interviewed James Grenning about why people are not doing technical practices sufficiently or well enough, why he thinks that TDD can be fun, the importance of unit tests, why programmers need to have a good nose for code smells and how they can become better in discovering "bad code”.

  • Coding Culture: How To Build Better Products by Building Stronger Teams

    Software developers spend a tremendous amount of time and energy focused on how to build the best possible products. We obsess over what web framework to use or whether to go with a NoSQL or SQL database. While these questions are important, they often neglect to address an equally important aspect of software development: culture.

  • Refactoring Coderetreats: In Search of Simple Design

    In cities all over the world, groups of software developers have been getting together at weekends repeatedly trying to write code for a given problem, but never completing a solution. At coderetreats, developers learn from each other and refine their software design skills. In this article David examines how they work? What do people say about them? How to make them even better?

BT