this post was submitted on 21 Jun 2023
4 points (100.0% liked)

Domain-Driven Design

258 readers
2 users here now

"Domain-Driven Design is an approach to software development that centers the development on programming a domain model that has a rich understanding of the processes and rules of a domain. The name comes from a 2003 book by Eric Evans that describes the approach through a catalog of patterns. Since then a community of practitioners have further developed the ideas, spawning various other books and training courses. The approach is particularly suited to complex domains, where a lot of often-messy logic needs to be organized." -- Martin Fowler (link)

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

founded 2 years ago
MODERATORS
snowe
canpolat
4
Technical debt isn't technical • Einar Høst • Devoxx UK (www.youtube.com)
submitted 2 years ago by canpolat to c/ddd
0 comments fedilink hide all child comments
 

cross-posted from: https://programming.dev/post/140226

This is a fun way to explain how technical debt accumulates in our systems. Not having good understanding of the domain results in low code quality and difficult to maintain code bases.

After the talk, one of the contributors says "you are preaching to the converted." But we, engineers, need to learn how to communicate these concerns with the rest of the organization.

no comments (yet)
sorted by: hot top controversial new old
there doesn't seem to be anything here