Resolving technical debts in software architecture

What's the single most critical action for resolving technical debt? This talk connects cognitive science to software architecture to reveal the answer.

#1about 6 minutes

How technical debt slows down feature development over time

Unmanaged technical debt leads to complex, tangled codebases, visualized as a "big ball of mud," which drastically reduces development velocity.

#2about 5 minutes

Quantifying code quality with the modularity maturity index

The Modularity Maturity Index (MMI) is a metric derived from tools like SonarQube to objectively measure the structural health and modularity of a software system.

#3about 4 minutes

Applying cognitive science principles to software design

Good software architecture aligns with how the human brain processes information through chunking, which translates directly to creating modular systems with high cohesion and loose coupling.

#4about 5 minutes

Leveraging design patterns and schemas for consistency

Using established design patterns consistently acts as a schema for developers, making the system easier to understand, navigate, and maintain.

#5about 3 minutes

Visualizing and enforcing architectural layering rules

Architecture review tools can visualize technical and domain layers, helping teams identify and fix violations like upward dependencies from the application layer to the UI.

#6about 2 minutes