Hendrik Lösch

Why (most) software projects fail silently...

Most software fails silently. It's not due to bad code, but a fundamental misunderstanding of value between business and tech.

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.

Software Engineer

tree-IT GmbH
Bad Neustadt an der Saale, Germany

Remote
Intermediate
Senior

Featured Partners

From learning to earning

Jobs that call for the skills explored in this talk.

Rust and GoLang

Rust and GoLang

NHe4a GmbH
Karlsruhe, Germany

Remote
55-65K
Intermediate
Senior
Go
Rust
Backend Engineer (m/w/d)

Backend Engineer (m/w/d)

fulfillmenttools
Köln, Germany

35-65K
Intermediate
TypeScript
Agile Methodologies
Google Cloud Platform