Domain Driven Design Podcast Summaries
Domain Driven Design on Yedapo: 4 summarized podcast and YouTube episodes. Each includes key takeaways, core concepts and notable quotes with timestamps.
Human Readable Code - Computerphile
Computerphile
May 29, 2026
Software engineers often build systems that are technically correct but misaligned with business requirements due to a communication gap. By adopting a 'fluent API' design, developers can create a shared, human-readable vocabulary within the code itself. This allows non-technical stakeholders to validate logic directly, ensuring the system solves the right problem from the start.
Key insight: Writing code as a series of readable English sentences—rather than a sequence of technical statements—serves as a powerful tool for verifying that the software's logic matches the business's actual intent.
ESDM: So coden wir alle in der Zukunft // deutsch
the native web GmbH
May 21, 2026
ESDM revolutioniert die Softwareentwicklung, indem es eine standardisierte, maschinenlesbare Sprache für DDD-Konzepte schafft. Anstatt nur Code zu generieren, erzwingt dieser Ansatz eine präzise fachliche Modellierung, die als 'Single Source of Truth' zwischen Anforderung und Implementierung dient.
Key insight: KI-generierter Code ist oft fehlerhaft, weil der Sprung von der natürlichen Sprache zur Implementierung zu groß ist; ESDM schließt diese Lücke, indem es als deterministische Zwischenschicht dient, die sowohl für Menschen lesbar als auch von Tools prüfbar ist.
I stopped using /grill-me for coding. Here’s what I use instead:
Matt Pocock
May 14, 2026
Generic prompting leads to hallucination and verbosity. By integrating Domain-Driven Design (DDD) principles—specifically ubiquitous language and ADRs—into an iterative AI 'grilling' session, you can achieve near-telepathic alignment between your intent and the AI's output.
Key insight: The same shared language that enables developers and domain experts to build software effectively also serves as the optimal mental model for Large Language Models to reduce token usage and improve code accuracy.
Modelagem de Software é Difícil? | "Ver" vs "Enxergar"
Fabio Akita
Aug 11, 2023
Fabio Akita argues that software modeling and architectural books are often useless for juniors because they lack the real-world mileage to understand the 'why' behind the patterns. True proficiency emerges only after years of building, maintaining, and evolving complex systems, not from memorizing theory.
Key insight: A typical entry-level e-commerce tutorial results in ~2,700 lines of code, while a production-grade platform like Magento requires ~2 million lines; reading books won't bridge that gap—only iterative, long-term experience with real-world business constraints will.
