Hendrik Lösch
Why (most) software projects fail silently...
#1about 2 minutes
Defining silent failure in software projects
Projects often fail from the very beginning due to accumulating issues, not from a single catastrophic event.
#2about 4 minutes
Translating software's unique properties for stakeholders
The intangible and complex nature of software, such as its replicability and changeability, creates a communication gap between developers and business stakeholders.
#3about 3 minutes
Balancing short-term features with long-term maintainability
Prioritizing rapid feature delivery without considering maintainability leads to increasing costs of change over the software's lifecycle.
#4about 4 minutes
The difference between restructuring and refactoring
Large-scale restructuring is a multi-year strategic effort to fix deep architectural issues, unlike small, incremental refactoring.
#5about 1 minute
Identifying non-technical debt in software projects
Technical debt is often a symptom of deeper issues like requirements debt, documentation debt, and testing debt.
#6about 6 minutes
Navigating the complete software product lifecycle
Software evolves through distinct phases including initial development, evolution, and servicing, each requiring different types of investment.
#7about 3 minutes
Overcoming cognitive biases in technical decision-making
Developers must be aware of survivorship, selection, and confirmation biases to avoid making flawed architectural and technology choices.
#8about 2 minutes
Aligning architecture with non-functional requirements
Architectural choices like microservices should be driven by specific quality attributes like scalability or reliability, not by industry trends.
#9about 2 minutes
Taking ownership to improve project outcomes
Developers can prevent silent failure by refusing to negotiate on code quality, integrating testing as a core practice, and consistently asking why.
Related jobs
Jobs that call for the skills explored in this talk.
Featured Partners
Related Videos
We (don't) need a software architect!?!
Hendrik Lösch
Modern software architectures
David Tielke
Resolving technical debts in software architecture
Carola Lilienthal
Unveiling the Dark Side: Navigating the Pitfalls of Digital Ambitions
Johannes Hansen
How to sabotage your software development with agile? – 10 pro tips for guaranteed success
Marlene Roth, Tobias Mohr
Breaking the Hardware Mindset: Overcoming Barriers to System-Level Innovation
Réka Leisztner
Seven Myths, Three Reasons, One Goal
Stefan Priebsch
Shipping Quality Software In Hostile Environments
Luka Kladaric
From learning to earning
Jobs that call for the skills explored in this talk.




Lead Software Architect
SDG Group
Municipality of Santiago de Compostela, Spain
Remote
API
Java
Azure
Scrum
+11
Software Architect (Contractor) - Composable Commerce & Event-Driven Design
CobbleWeb
Birmingham, United Kingdom
Remote
€61K
Redis
React
Node.js
+4





