Quality is no coincidence
Living quality as an attitude, not just writing test cases: Why it makes the difference and what 150 podcast episodes teach about it.
Living quality as an attitude, not just writing test cases: Why it makes the difference and what 150 podcast episodes teach about it.
Changing one word in your feedback can shift a conversation from conflict to clarity. Here's how nonviolent communication works in real testing teams.
From the embassy to software testing: what really helps when making a career change and why certificates alone won't get you a job.
Teaching software testing to 120 students means skipping dry test plans and starting with automation, APIs, and performance testing instead.
Developer friendliness costs time in the short term, but saves it in the long term - and makes teams measurably happier. REST mocks and test interfaces from a real project show what this means in concrete terms.
Good ideas don't fail because of logic. They fail because change is emotional, and most leaders only speak to the cognitive side.
Risk-based testing works - but only if it's more than a gut feeling. Five levels, one aggregated score, zero extra effort.
Bringing external testers into the agile team - in one week? How this works with contingents, clear communication and a fixed contact person.
Agile quality often breaks not in the team, but one layer above. How practices, not frameworks, keep quality from falling through the cracks.
Those who build software without asking users beforehand are often solving the wrong problem. What product discovery actually means and why paper prototypes beat real code.
A bug that only appears after 17 exact steps sounds untestable. Property-based testing finds it anyway, by generating cases humans would never think to write.
Anyone who installs open source components needs a bill of materials - because 80 to 95 percent of modern software is in them. What licenses, security vulnerabilities and the Cyber Resilience Act have to do with it.
Security built in from the start beats security bolted on at the end. Here is why threat modeling, defense in depth, and secure defaults change everything.
A third of respondents already use AI for coding, but many still lack automation when it comes to regression testing. What the Software Testing Survey 2024 really shows.
Most software problems start as conversations that never happened. Collaborative modeling shows how to fix alignment before it hardens into broken code.
Static analysis throws up thousands of findings - AI fixes two thirds of them reliably. What this means for old code bases and where the method clearly reaches its limits.
Psychological safety can be built, but one careless remark can undo weeks of progress. Here's how teams solve problems together.
Why do retrospectives so often produce the same little pieces of paper? Five phases, a design canvas and a crucial error in thinking about the measures.