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
Identifying and eliminating harmful cyclic dependencies
Cyclic dependencies between classes or modules create tangled structures that grow over time and must be refactored early to maintain system health.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
02:34 MIN
Addressing the challenge of growing software complexity
Model Based Systems Engineering in an Agile Product Development Process
06:06 MIN
Understanding and managing the impact of technical debt
Move fast with Software Architecture
03:45 MIN
Recognizing the root causes of technical debt
We (don't) need a software architect!?!
03:37 MIN
Preventing architectural decay and code structure issues
Antipatterns - nemesis of software development
09:48 MIN
Reframing the technical debt dilemma for continuous improvement
Single Server, Global Reach: Running a Worldwide Marketplace on Bare Metal in a Cloud-Dominated World
03:57 MIN
Achieving sustainable software architecture for long-term productivity
It’s all about the domain, honey ! Experiences from 15 years of Domain-Driven Design
04:24 MIN
The challenge of justifying legacy system improvements
Data Science on Software Data
09:25 MIN
Key principles for managing long-term technical debt
The real reason we document our codeThe world of software development moves fast. Technology is constantly changing, as are the tools we use with it, and even the role of a programmer is itself constantly in flux. However, some aspects of software engineering are so foundational that w...
Benedikt Bischof
Why You Shouldn’t Build a Microservice ArchitectureWelcome to this issue of the WeAreDevelopers Live Talk series. This article recaps an interesting talk by Michael Eisenbart who talks about the pros and cons of microservice architecture.About the speaker:Michael has been working for Bosch as a sof...
Benedikt Bischof
How we Build The Software of TomorrowWelcome to this issue of the WeAreDevelopers Live Talk series. This article recaps an interesting talk by Thomas Dohmke who introduced us to the future of AI – coding.This is how Thomas describes himself:I am the CEO of GitHub and drive the company’s...
Chris Heilmann
Processing 175 WeAreDeveloper World Congress talk videos in 5 hours - with PHP?Every year after the WeAreDevelopers World Congress is over, we have a ton of video footage to edit and release. Most of it is in raw format and needs editing by hand, but a lot of our sessions are also streamed live on YouTube and thus easier to re-...
From learning to earning
Jobs that call for the skills explored in this talk.
26:22
43:13
24:52
28:17
42:02
30:23
25:40
39:49
.gif?w=240&auto=compress,format)
