Published May 29, 2017

The Domain in Domain Driven Design

Explore the essence of Domain Driven Design as Joe Zack and Michael Outlaw dissect entities, value objects, and domain services, navigate the choices in developer laptops and headphones, and grapple with the trade-offs between quick fixes and technical debt in programming.
Episode Highlights
Coding Blocks logo

Popular Clips

Episode Highlights

  • Quick Decisions

    The conversation between and explores the balance between quick coding solutions and sustainable code. Joe argues that quick and dirty solutions can be more beneficial than perfect solutions that are never completed. He shares, "I do quick and dirty stuff all the time, and I don't feel bad because quick and dirty is better than correct or perfect and never done" 1. Michael adds that while quick solutions can be agile, they may not always be developer-friendly, as they often require adapting existing systems without fully integrating them 2.

       

    Technical Debt

    The discussion shifts to the implications of technical debt in software projects. Joe highlights the danger of continuously postponing necessary improvements, likening it to "kicking the can down the road" until it becomes insurmountable 3. Michael clarifies that not all quick solutions result in technical debt, as some may be the perfect approach for the situation at hand. He emphasizes the importance of evaluating whether a quick fix will need to be revisited or expanded in the future, which can transform a simple solution into a complex problem if not managed properly 3.

Related Episodes