We (don't) need a software architect!?!

Every development team creates an architecture. The only choice is whether it's planned or unplanned—and the consequences are massive.

#1about 4 minutes

Bridging the communication gap between stakeholders

Software's unique properties like invisibility and changeability create a communication gap between internal technical teams and external business stakeholders.

#2about 3 minutes

Understanding the core cycle of an architect's work

An architect's role involves a continuous cycle of gathering requirements, designing solutions, evaluating them, and verifying the final implementation.

#3about 3 minutes

Using ISO 25010 to define non-functional requirements

The ISO 25010 standard provides a framework for defining crucial non-functional requirements that guide architectural decisions like choosing a monolith for performance.

#4about 4 minutes

Recognizing the root causes of technical debt

Unplanned architecture leads to technical debt, which is often a symptom of deeper issues like missing requirements and a lack of documentation.

#5about 4 minutes

Navigating the complete software evolution lifecycle

Software evolves through phases from initial development and feature addition to servicing and eventual phase-out, with early decisions impacting its entire lifespan.

#6about 2 minutes

Differentiating between refactoring and restructuring legacy code

Small, safe changes are refactoring, while large-scale changes like cloud migration are restructuring projects that require significant planning and investment.

#7about 3 minutes