BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Software Craftsmanship Content on InfoQ

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

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

  • When the Jobs Go Marching in

    Alex discusses the rising demand for IT workers in the next decades and the implications of the different approaches employed by people to fulfill this demand. It introduces the distinction between “professionals” and “practitioners”, discusses the possible different outcomes from each group as they are embedded within businesses, and provides some recommendations.

  • Q&A on The Rise and Fall of Software Recipes

    Darius Blasband has written a book which challenges the conventional wisdom of software engineering: he protests against the adoption of recipes and standards-based approaches and rails against the status-quo. He calls himself a codeaholic who advocates for careful consideration of the specific context and the use of domain specific languages wherever possible.

  • Q&A on The Manager‘s Path with Camille Fournier

    In the book The Manager’s Path, Camille Fournier explores managing engineers and what it takes to be a technical manager. She describes the different roles which form the path from mentors and tech leads to senior engineering management, discusses the challenges of technical leadership and provides advice on how to deal with them.

  • How to Sell Refactoring? The Case of Nordea Bank AB

    Refactoring is often not a technical challenge. Teams can accurately diagnose inefficient code design. If they have sufficient time and budget at their disposal, they would probably get things done. In this article, we focus on the strategic code refactoring. This distinction was introduced by the BNS IT consultants as part of the method called Natural Course of Refactoring.

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

  • Enhance Your Testing Skills with Mindset Tools

    Quite a lot of testers often miss out on the mindset necessary for the testing and delivery of quality products. Sometimes it seems that quality consciousness is missing. This article is about how I discovered a way to grow my test mindset, and how my discovery has been useful in enhancing my testing skills.

  • Using Structured Conversations to Discover Your MVP

    In an increasingly more complex world, finding the smallest possible chunk to deliver to get feedback is essential. This is the idea behind the term MVP. This article describes a model where business and technology together explore the product needs along seven product dimensions, which is a great way of finding small slices of work to develop.

  • Predictable Agile Delivery: The Executive Challenge

    As agile grows-out of its years of self-obsession and teenage petulance into a post-agile state, ‘Predictable Agile Delivery’ feels like a realistic goal that advantages both the business sponsor and their development stakeholders. This article shares some ‘good, bad and ugly’ examples of practices that often work and some that always fail at improving large organizations.

  • Developing Quality Software: Differentiating Factors

    The level of software quality attainable is a reflection of an organizational business decision. There are many factors that influence this decision, including development, build and testing environments effectiveness, resources and their associated skillset, integrity, motivations and experience levels, commercial agreements, and adopted processes and productivity tools.

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

BT