
About this episode
How technical is technical debt? Carl and Richard talk to Einar Høst about how technical debt has more to do with your understanding of a system and the intentional shortcuts we take to make deadlines than anything specific to technology. The conversation dives into the domain driven design thinking of Eric Evans and the challenges of deeply understanding the domain of a system well enough to build great software to model it. As Einar puts it, some complexity is intentional, and some is accidental. That accidental complexity can be considered technical debt, but it is always challenging to measure it. In the end, the key is communications!
Support this podcast at — https://redcircle.com/net-rocks/donations
Support this podcast at — https://redcircle.com/net-rocks/donations
Get every episode summarized
Each time .NET Rocks! publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from .NET Rocks!

Post-Quantum Crypto with Michael Howard
.NET Rocks!
Sep 3, 20261:05:51completed

Numerics.NET with Jeffrey Sax
.NET Rocks!
Sep 3, 20261:05:07completed

Constraining Agents for Software Development with Don Demcsak
.NET Rocks!
Sep 2, 20261:00:05failed

Arguing about AI with Billy Hollis
.NET Rocks!
Aug 26, 20261:03:03pending