Why Domain Driven Design

Topics covered
Popular Clips
Episode Highlights
Listener Input
Listener contributions have sparked engaging discussions and insights on the podcast. shared a listener's recommendation of regex tools, highlighting refiddle.com and regexer.com as valuable resources for developers. He expressed gratitude for the listener's input, emphasizing the collaborative nature of the community 1. recounted his experience speaking at the Atlanta JavaScript meetup, where he followed a highly polished presentation with numerous demos 2. Despite the challenge, Alan's presentation was well-received, showcasing the supportive environment fostered by the podcast's audience.
  Â
Feedback
Audience feedback plays a crucial role in refining the podcast's content. acknowledged a user correction regarding a previous episode's technical error, demonstrating the active engagement of listeners 3. addressed another correction about SSD speeds, clarifying a misunderstanding about gigabits and gigabytes per second 4. These interactions highlight the podcast's commitment to accuracy and the value of listener contributions in maintaining high-quality discussions.
Related Episodes


The Domain in Domain Driven Design
Answers 383 questions

Strategic Design and Domain Events
Answers 383 questions

Clean Code - How to Build Maintainable Systems
Answers 383 questionsDesign Patterns Part 3
Answers 383 questions

Software Design Anti-patterns
Answers 383 questionsClean Code - How to Write Amazing Functions
Answers 383 questions

Clean Code - How to Write Classes the Right Way
Answers 383 questionsDesign Patterns Part 1
Answers 383 questionsHow to be a Programmer
Answers 383 questionsWhat is Supple Design?
Answers 383 questionsDesigning Data-Intensive Applications – Scalability
Answers 383 questions
Tackling Tough Developer Questions
Answers 383 questionsWhy Date-ing is Hard
Answers 383 questionsHow to be an Advanced Programmer
Answers 383 questions

Keyboards, Cloud Costs, Static Analysis, and Philosophy
Answers 383 questions
