BOUNDARYLESS CONVERSATIONS PODCAST — SEASON 4 EP #12

On Domain-Driven Design and the challenges of reaching Agreements — with Alberto Brandolini

Alberto Brandolini joins the podcast as a sparring partner in our exploration of one of the most “burning” issues in our research: the intrinsic links between language, software and organizational design. We explore the role of domain-driven design and, more generally, the role of visualization and context mapping in the process that we call “ontological convergence” i. e. how we agree on standards, converge on using common models and build common tools, protocols and infrastructures.

Boundaryless

Published in

Stories of Platform Design

3 min readMar 21, 2023

Podcast notes

Alberto, EventStorming creator, Domain-Driven Design (DDD) legend and unconventional entrepreneur, is also famous for the Bullshit Asymmetry Principle aka Brandolini’s law. He proudly runs Avanscoperta, a hub for inventing, promoting, and spreading new ideas around software development. Alberto is also a frequent speaker at conferences and events, and an international trainer with more than ten years of experience.

During the chat we explore the ways software drives the adoption of common models and languages, and how the boundaries between technology and business, between one team and another, and even between organizations themselves, are blurring.

Alberto observes that the more you go distributed, the more having clean, well-visualized “bounded contexts” really becomes a key factor in the effectiveness and success of organizations. Defining components and modules reduces the need to collectively agree about stuff: a heavily underestimated cost of organizing.

Remember that you can always find transcripts and key highlights of the episode on our website: https://boundaryless.io/podcast/with-alberto-brandolini/

Key highlights

👉 How ubiquitous can language be
👉 The best way to speed up reaching agreement? Visualizing instead of talking.
👉 Most no-code and low-code approaches are designed around a paradigm that is antithetic to domain-driven design.
👉 Domain-driven design suggests to be aware of the cost of your architectural decisions and the evolutions of these forces over time
👉 When the quality of a component makes it an obvious choice, it’s a good way to create standards
👉 The hardest part for remote-first organizations is finding a way to make distributed decisions on critical issues

Topics (chapters):

(00:00) Alberto Brandolini quote
(00:56) Alberto Brandolini introduction
01:33 What domain-driven design is
16:14 The cost-benefit of agreeing
24:05 Domain-driven design approach in complex environment
28:19 How no-code and low-code system relate to DDD
38:28 The role of DDD in driving standards into markets and ecosystems
48:22 Talent useful for a company like Avanscoperta
51:24 Alberto Brandolini’s breadcrumbs