The Domain in Domain Driven Design

Topics covered
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


Why Domain Driven Design
Answers 383 questions

Strategic Design and Domain Events
Answers 383 questions

Keyboards, Cloud Costs, Static Analysis, and Philosophy
Answers 383 questions
Tackling Tough Developer Questions
Answers 383 questions

Designing Data-Intensive Applications - Data Models: Relational vs Document
Answers 383 questionsWhat is Supple Design?
Answers 383 questionsDesign Patterns Part 1
Answers 383 questions

Clean Code - How to Write Classes the Right Way
Answers 383 questions

Clean Architecture - Programming Paradigms
Answers 383 questionsClean Code - How to Write Amazing Functions
Answers 383 questions

Docker Licensing, Career and Coding Questions
Answers 383 questions

Data Structures - Arrays and Array-ish
Answers 383 questionsDesign Patterns Part 3
Answers 383 questions

Software Design Anti-patterns
Answers 383 questions

The Pragmatic Programmer - How to Build Pragmatic Teams
Answers 383 questions
