Projects often fail from the very beginning due to accumulating issues, not from a single catastrophic event.
The intangible and complex nature of software, such as its replicability and changeability, creates a communication gap between developers and business stakeholders.
Prioritizing rapid feature delivery without considering maintainability leads to increasing costs of change over the software's lifecycle.
Large-scale restructuring is a multi-year strategic effort to fix deep architectural issues, unlike small, incremental refactoring.
Technical debt is often a symptom of deeper issues like requirements debt, documentation debt, and testing debt.
Software evolves through distinct phases including initial development, evolution, and servicing, each requiring different types of investment.
Developers must be aware of survivorship, selection, and confirmation biases to avoid making flawed architectural and technology choices.
Architectural choices like microservices should be driven by specific quality attributes like scalability or reliability, not by industry trends.
Developers can prevent silent failure by refusing to negotiate on code quality, integrating testing as a core practice, and consistently asking why.
24:52Hendrik Lösch
26:22David Tielke
24:38Carola Lilienthal
21:39Johannes Hansen
29:03Marlene Roth & Tobias Mohr
46:48Stefan Priebsch
28:28Réka Leisztner
25:40Julian Lang
.png?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
IKEA
Amsterdam, Netherlands
Speech Processing Solutions
Vienna, Austria
Saby New Compy
Bielefeld, Germany
Software Quality