Season Four Wrap: Whose Design Is It Anyway? with Swadia, Windholtz, Rezentes, and Keathley

About this Episode

Published October 15, 2020 | Duration: 59:12 | RSS Feed | Direct download
Transcript: English

To close off this season and conclude our deep dive into system and application architecture, today’s episode is a special panel discussion on a topic that has provoked a mix of answers that range from the controversial to the philosophical — “What does domain-driven design mean to you?” For the final word on this subject, we welcome back software developers Chris Keathley, Japa Swadia, Mark Windholtz, and Miki Rezentes. Our first hot take comes from Miki, who shares her thoughts about how domain-driven design developed because the tech industry undervalues communication. Following this, Mark and Japa discuss how domain-driven design gives developers a context for what they create while informing how you code using Elixir. We then touch on whether domain-driven design makes it easier or more difficult to change your code and how communication is valued within a business context. We explore key domain-driven design concepts, including the role of bounded contexts, and how this design ethos can help you appeal to stakeholders such as product managers. After Miki highlights the reasons why communication should be seen as a vital tech skill, each guest provides their final thoughts on domain-driven design. Tune in for this season’s insightful finale and find out which of today’s guests is the winner of “Whose Design Is It Anyway?”

Key Points From This Episode:

  • Introducing guests Chris Keathley, Japa Swadia, Mark Windholtz, and Miki Rezentes.
  • Hear what domain-driven design means for each guest.
  • Miki shares her hot take that domain-driven design is “nothing new under the sun.”
  • Why the essence of domain-driven design is about listening.
  • How domain-driven design can inform your Elixir architecture.
  • Mapping your system and developing names for your bounded contexts.
  • Domain-driven design trade-offs and how it can lead to a loss of productivity.
  • The idea that domain-driven design has developed because the tech industry undervalues communication.
  • Why communication should be valued — bad communication costs money.
  • How tech companies are generally aligned with the goals of domain-driven design.
  • Why Mark is so delighted to be working with Elixir and domain-driven design.
  • The link between domain-driven design and developing better products.
  • Exploring how bounded contexts allow teams to create solutions to unique problems.
  • Seeing communication as a tech skill that should be learned early in your career.
  • Our guests share their final thoughts on domain-driven design.

Links Mentioned in Today’s Episode:

SmartLogic —
Chris Keathley on Twitter — @ChrisKeathley/
Chris Keathley —
Japa Swadia on Twitter —
Japa Swadia on LinkedIn —
Mark Windholtz on Twitter —
Mark Windholtz on LinkedIn —
Miki Rezentes on Twitter —
Miki Rezentes on LinkedIn —
Podium —
Elixir Outlaws —
Agile DNA — —
Bleacher Report —
Domain-Driven Design: Tackling Complexity in the Heart of Software on Amazon—
Domain Language —
The Seven Laws of Learning: Why Great Leaders Are Also Great Teachers on Amazon
Patterns, Principles, and Practices of Domain-Driven Design on Amazon —
‘Ubiquitous Language’ —
‘Value Object’ —
Domain-Driven Design Europe —
Domain-Driven Design Europe on YouTube —
A Philosophy of Software Design on Amazon —
Eric Evans Training Videos —
Designing Elixir Systems with OTP —
Whose Line Is It Anyway? —
Drew Carey —

Special Guests: Chris Keathley, Japa Swadia, and Miki Rezentes.

Transcript (English):