InfoQ Homepage Software Craftsmanship Content on InfoQ
-
How King uses AI to test Candy Crush Saga
To be able to improve features in games which are constantly evolving, the challenge will be to scale tests to be on a par with new feature development. Automated tests are vital for King to keep up testing Candy Crush, therefore they are constantly looking for new improved ways to test.
-
Q&A on the Book Team Topologies
The book Team Topologies by Matthew Skelton and Manuel Pais shows how to arrange teams within an organization to enable effective software delivery. It describes four fundamental team types and three team interaction patterns, and dives into the responsibility boundaries of teams and how teams can communicate or interact with other teams.
-
Categorise Unsolved Problems in Agile Development: Premature & Foreseeable
Productivity decline and technical debt, as often seen in agile development, can be prevented by separating unsolved problems into premature and foreseeable. It shifts the discussion about unsolved problems from importance to likelihood. With small but essential adjustments, agile can be kept sustainable. With this insight, developer-architect differences and team psychology gaps can be bridged.
-
Q&A on the Book Managing Technical Debt
The book Managing Technical Debt by Philippe Kruchten, Robert Nord, and Ipek Ozkaya provides principles and practices that help you gain control of technical debt throughout the software development process and life of the software product.
-
Test Automation: Prevention or Cure?
A lot of teams have the tendency to view test automation as a way of speeding up delivery of software, as this is often the perceived bottleneck within the team, but if they were to take a deeper look at their development practices as a whole, they may get better results.
-
Simplicity, Please - A Manifesto for Software Development
An unrelenting and breathless rush to market is quietly driving your company to the brink of extinction. Maybe it’s time to rethink how you design and write code. Investment in simplicity is investment in speed. Simplicity is also the mother lode of intellectual property — and a competitive advantage almost impossible to regain once lost.
-
Who is in Charge of Quality in Software Development
As silos break down, the whole team is responsible for quality in software development. As process more and more defines people and processes, how can you strive for better quality of releases?
-
Test Automation in the World of AI & ML
An in-depth look at the criteria & requirements for Functional Test Automation in the agile world, and the capabilities you should build in your custom framework, or should exist the tools you choose. Anand Bagmar explores aspects like readability, reuse, debugging / rca, CI, Test Data, Parallel Execution, integration with other tools & libraries, free Vs open-source and support.
-
Q&A on the Book Refactoring - Second Edition
The book Refactoring - Second Edition by Martin Fowler explores how you can improve the design and quality of your code in small steps, without changing external behavior. It consists of around seventy detailed descriptions of refactorings, including a motivation for doing them, the mechanics, and an example.
-
How to Slow Down to Go Faster Than Ever in Software Development
Going fast without control could be the biggest enemy of software development. By slowing down on people, we improve professionalism and craftsmanship. By slowing down on process, we improve adaptation and efficiency. And by slowing down on product, we improve automation and quality. When we focus on these areas, we start to cultivate a development culture enabling software development fast.
-
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.
-
Testing Programmable Infrastructure - a Year On
Programmable infrastructure is becoming widespread. There are very specific domain issues that make testing it tricky. This article looks at the evolution of tooling and approaches used to address it.