Software engineering in the year 2034
AI doesn't make developers more productive, it makes them faster at creating legacy code. What this means for quality and jobs until 2034.
AI doesn't make developers more productive, it makes them faster at creating legacy code. What this means for quality and jobs until 2034.
From July 2025, penalties of up to 100,000 euros will be imposed for lack of accessibility. What this means in concrete terms for design, development and testing.
There is often a gap between theory and practice in software testing. How AI-supported certification aims to change this - and why 40 national boards are getting involved.
Explore how sustainability in IT and eco-friendly IT solutions can optimize resource use for better performance. Small changes, big impact!
LLMs testing like a pro: Acceptance Test Driven Development meets fine-tuning - creating a measurable quality process for AI systems.
Without a test structure, without a budget, without ready-made tools: How one team built real quality assurance step by step.
A test automation monolith that has grown for years, XML everywhere in the code like a tumor: How to refactor anyway and what really counts.
Stoic principles in product management: Those who judge decisions by the result make the wrong judgment. Three lessons that change that.
Lots of unit tests, high test coverage, but still bugs. Why the test pyramid is often used incorrectly and when other approaches make more sense.
Separating functional and quality requirements: useful or misleading? What this distinction really means for architecture decisions.
Anyone who plans acceptance testing shortly before delivery is testing quality at the most expensive time. What early integration really brings.
Test strategy via workshop instead of a hundred-page document: How a collaborative format quickly brings teams to a common test picture.
Why should the earth be a stakeholder in the next sprint? Sustainable software saves costs, conserves resources and makes systems better for everyone.
Since 2011, the German Testing Day has combined practical experience, an independent board and unusual keynotes - what sets this conference apart from the rest.
Those who accept software usually only test functions. Whether up to 12,000 undiscovered bugs are normal and what "state of the art" really means in legal terms.
Conflicts in a team are not a disruption - they are energy. How to recognize them early, address them correctly and use them for the team.
One year, 67 episodes, over 22,000 downloads: What became of a spontaneous video idea and where the journey will take us next.
Scrum provides a process, but not a plan for good requirements. What happens before the backlog often determines product success more than any sprint.