Engineering brief
Growing & Thriving in a Multi-model World • Alberto Brandolini • GOTO 2025
This engineering brief covers Growing & Thriving in a Multi-model World • Alberto Brandolini • GOTO 2025, with practical context for AI and developer-tool decisions.
The Brief
Domain-driven design with bounded contexts prevents software decay, but teams resist splitting models until too late.
Decision relevance
Read this for workflow impact, implementation trade-offs, and the claims that need technical scrutiny before they reach team planning.
Summary
Alberto Brandolini delivers a career-spanning reflection on why single, unified domain models inevitably fail and how multi-model approaches built around bounded contexts are the antidote—but one that requires unnatural discipline to sustain. The core argument: software naturally trends toward a 'big ball of mud' because our brains default to verbal, data-centric thinking that ignores purpose. Teams merge unrelated concepts (e.g., invoices and forecasts), creating models that serve too many stakeholders, accumulate fear of change, and eventually produce the classic plateau where more investment yields diminishing returns. Brandolini distills a decade of experience from his own company into practical countermeasures: never modify a working bounded context; never make design decisions without a visual map; always generate three alternatives before choosing a solution; and use context maps to detect the real friction points—whether business value, aesthetic ugliness, or fear. The talk extends into multi-market scenarios, dissecting why the 'second country' implementation always fails when it inherits a brownfield codebase with a junior team. It also challenges the authority of domain experts, regulators, and business timelines, arguing that software teams must own their models rather than replicating external narratives. The most transferable insight: teams should split when signals are clear and decisions are cheap, not when scaling forces their hand. The session is rich with psychological observations about modeling—visual anchoring outperforms verbal reasoning, and addiction-replacement patterns can reshape team habits. Missing are empirical benchmarks or controlled comparisons; the evidence is auto-ethnographic, drawn from consulting and a single long-lived internal project. That doesn't invalidate the lessons, but it limits generalizability. Engineering managers will find the most value in the practical decision-making heuristics and the framing of fear as a legitimate architectural driver. The final minutes rush through multi-country domain expertise, leaving the most novel ideas underdeveloped.
Why It Matters
The natural drift toward monolithic models silently kills delivery speed. Teams need explicit discipline and visual tools to resist it.
Editorial analysis
Key claims
- Use bounded contexts and visual maps early, split by purpose, and treat fear as a legitimate architectural signal.
Practical use cases
- Use this as input for tooling evaluation, workflow planning, and technical due diligence.
Risks / caveats
- The rushed ending on multi-country modeling lacks the depth of the earlier, more practical insights.
Who should care
- Engineering managers, tech leads, and CTOs evaluating AI or developer tooling decisions.
Related topics
Bottom Line
Use bounded contexts and visual maps early, split by purpose, and treat fear as a legitimate architectural signal.
Watch
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
The Alignment Trap: Why Technical Leadership Isn’t Senior Coding
Tech leadership is about alignment, not architecture. Kua’s framework shows how to spot misalignment, own it, and reduce complexity across teams.
ARM Adoption: The Cost Win Nobody Can Ignore
ARM instances cut cloud costs up to 40% and .NET is ready. Learn the migration cheat sheet, case studies, and key tradeoffs for ARM adoption.
Flaky Tests Ruin More Than Velocity—They Kill Trust
This talk deconstructs how better test design and tooling—not more AI—speed up delivery.
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.