home.social

#domaindrivendesign — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #domaindrivendesign, aggregated by home.social.

fetched live
  1. A year ago today, @roundcrisis, @ahl and I published the first episode of Stories on Facilitating Software Architecture & Design. Yesterday episode 27 went out. We've kept it going every two weeks since.

    We didn't start it to publish content. We started it because the work engineers are being asked to do is changing, and most people are working that out on their own.

    #SoftwareArchitecture #DomainDrivenDesign

  2. A year ago today, @roundcrisis, @ahl and I published the first episode of Stories on Facilitating Software Architecture & Design. Yesterday episode 27 went out. We've kept it going every two weeks since.

    We didn't start it to publish content. We started it because the work engineers are being asked to do is changing, and most people are working that out on their own.

    #SoftwareArchitecture #DomainDrivenDesign

  3. A year ago today, @roundcrisis, @ahl and I published the first episode of Stories on Facilitating Software Architecture & Design. Yesterday episode 27 went out. We've kept it going every two weeks since.

    We didn't start it to publish content. We started it because the work engineers are being asked to do is changing, and most people are working that out on their own.

    #SoftwareArchitecture #DomainDrivenDesign

  4. A year ago today, @roundcrisis, @ahl and I published the first episode of Stories on Facilitating Software Architecture & Design. Yesterday episode 27 went out. We've kept it going every two weeks since.

    We didn't start it to publish content. We started it because the work engineers are being asked to do is changing, and most people are working that out on their own.

    #SoftwareArchitecture #DomainDrivenDesign

  5. A year ago today, @roundcrisis, @ahl and I published the first episode of Stories on Facilitating Software Architecture & Design. Yesterday episode 27 went out. We've kept it going every two weeks since.

    We didn't start it to publish content. We started it because the work engineers are being asked to do is changing, and most people are working that out on their own.

    #SoftwareArchitecture #DomainDrivenDesign

  6. Kruglanski's work on cognitive closure describes this pull. He wasn't writing about software boundaries. The pattern is the same.

    Holding the discomfort is only half of it though. Hold it too long and the group is just tired. The other half is reading when the not knowing has done its work and closing there. That balance is a skill, and it gets better with practice.

    Anyone can pick it up. What doesn't work is assuming someone will.

    #DomainDrivenDesign #CollaborativeModelling #Facilitation

  7. Kruglanski's work on cognitive closure describes this pull. He wasn't writing about software boundaries. The pattern is the same.

    Holding the discomfort is only half of it though. Hold it too long and the group is just tired. The other half is reading when the not knowing has done its work and closing there. That balance is a skill, and it gets better with practice.

    Anyone can pick it up. What doesn't work is assuming someone will.

    #DomainDrivenDesign #CollaborativeModelling #Facilitation

  8. Kruglanski's work on cognitive closure describes this pull. He wasn't writing about software boundaries. The pattern is the same.

    Holding the discomfort is only half of it though. Hold it too long and the group is just tired. The other half is reading when the not knowing has done its work and closing there. That balance is a skill, and it gets better with practice.

    Anyone can pick it up. What doesn't work is assuming someone will.

    #DomainDrivenDesign #CollaborativeModelling #Facilitation

  9. Kruglanski's work on cognitive closure describes this pull. He wasn't writing about software boundaries. The pattern is the same.

    Holding the discomfort is only half of it though. Hold it too long and the group is just tired. The other half is reading when the not knowing has done its work and closing there. That balance is a skill, and it gets better with practice.

    Anyone can pick it up. What doesn't work is assuming someone will.

    #DomainDrivenDesign #CollaborativeModelling #Facilitation

  10. Kruglanski's work on cognitive closure describes this pull. He wasn't writing about software boundaries. The pattern is the same.

    Holding the discomfort is only half of it though. Hold it too long and the group is just tired. The other half is reading when the not knowing has done its work and closing there. That balance is a skill, and it gets better with practice.

    Anyone can pick it up. What doesn't work is assuming someone will.

    #DomainDrivenDesign #CollaborativeModelling #Facilitation

  11. Subdomain, bounded context, service. Three different boundaries, drawn by different people, for different reasons.

    A bounded context is a language boundary. A service is a deployment boundary. Picking one and assuming the other two came for free is where most of the pain starts.

    @selketjah and I are speaking about this at KanDDDinsky, Berlin, 14 to 16 October.

    kandddinsky.de/2026/sessions/d

    #DomainDrivenDesign #SoftwareArchitecture

  12. Subdomain, bounded context, service. Three different boundaries, drawn by different people, for different reasons.

    A bounded context is a language boundary. A service is a deployment boundary. Picking one and assuming the other two came for free is where most of the pain starts.

    @selketjah and I are speaking about this at KanDDDinsky, Berlin, 14 to 16 October.

    kandddinsky.de/2026/sessions/d

    #DomainDrivenDesign #SoftwareArchitecture

  13. Subdomain, bounded context, service. Three different boundaries, drawn by different people, for different reasons.

    A bounded context is a language boundary. A service is a deployment boundary. Picking one and assuming the other two came for free is where most of the pain starts.

    @selketjah and I are speaking about this at KanDDDinsky, Berlin, 14 to 16 October.

    kandddinsky.de/2026/sessions/d

    #DomainDrivenDesign #SoftwareArchitecture

  14. Subdomain, bounded context, service. Three different boundaries, drawn by different people, for different reasons.

    A bounded context is a language boundary. A service is a deployment boundary. Picking one and assuming the other two came for free is where most of the pain starts.

    @selketjah and I are speaking about this at KanDDDinsky, Berlin, 14 to 16 October.

    kandddinsky.de/2026/sessions/d

    #DomainDrivenDesign #SoftwareArchitecture

  15. Subdomain, bounded context, service. Three different boundaries, drawn by different people, for different reasons.

    A bounded context is a language boundary. A service is a deployment boundary. Picking one and assuming the other two came for free is where most of the pain starts.

    @selketjah and I are speaking about this at KanDDDinsky, Berlin, 14 to 16 October.

    kandddinsky.de/2026/sessions/d

    #DomainDrivenDesign #SoftwareArchitecture

  16. I'm speaking at KanDDDinsky 2026 in Berlin this October.

    KanDDDinsky is one of the few conferences where the hallway conversations are as good as the ones on stage. That isn't an accident. The whole thing is set up so practitioners learn from each other rather than sit and listen. Working software, real problems, no vendor pitches.

    A lot of this year's programme deals with AI in business software: what it actually gives us, and what it costs us. Both parts matter and both get discussed honestly. If you build business software for a living, this is your crowd.

    14-15 October, Park Inn at Alexanderplatz. Early-bird tickets are 800 EUR until this Friday, 31 July. After that they go up to 950 EUR.

    kandddinsky.com/

    #KanDDDinsky #DDD #DomainDrivenDesign #SystemsThinking

  17. I'm speaking at KanDDDinsky 2026 in Berlin this October.

    KanDDDinsky is one of the few conferences where the hallway conversations are as good as the ones on stage. That isn't an accident. The whole thing is set up so practitioners learn from each other rather than sit and listen. Working software, real problems, no vendor pitches.

    A lot of this year's programme deals with AI in business software: what it actually gives us, and what it costs us. Both parts matter and both get discussed honestly. If you build business software for a living, this is your crowd.

    14-15 October, Park Inn at Alexanderplatz. Early-bird tickets are 800 EUR until this Friday, 31 July. After that they go up to 950 EUR.

    kandddinsky.com/

    #KanDDDinsky #DDD #DomainDrivenDesign #SystemsThinking

  18. I'm speaking at KanDDDinsky 2026 in Berlin this October.

    KanDDDinsky is one of the few conferences where the hallway conversations are as good as the ones on stage. That isn't an accident. The whole thing is set up so practitioners learn from each other rather than sit and listen. Working software, real problems, no vendor pitches.

    A lot of this year's programme deals with AI in business software: what it actually gives us, and what it costs us. Both parts matter and both get discussed honestly. If you build business software for a living, this is your crowd.

    14-15 October, Park Inn at Alexanderplatz. Early-bird tickets are 800 EUR until this Friday, 31 July. After that they go up to 950 EUR.

    kandddinsky.com/

  19. I'm speaking at KanDDDinsky 2026 in Berlin this October.

    KanDDDinsky is one of the few conferences where the hallway conversations are as good as the ones on stage. That isn't an accident. The whole thing is set up so practitioners learn from each other rather than sit and listen. Working software, real problems, no vendor pitches.

    A lot of this year's programme deals with AI in business software: what it actually gives us, and what it costs us. Both parts matter and both get discussed honestly. If you build business software for a living, this is your crowd.

    14-15 October, Park Inn at Alexanderplatz. Early-bird tickets are 800 EUR until this Friday, 31 July. After that they go up to 950 EUR.

    kandddinsky.com/

    #KanDDDinsky #DDD #DomainDrivenDesign #SystemsThinking

  20. I'm speaking at KanDDDinsky 2026 in Berlin this October.

    KanDDDinsky is one of the few conferences where the hallway conversations are as good as the ones on stage. That isn't an accident. The whole thing is set up so practitioners learn from each other rather than sit and listen. Working software, real problems, no vendor pitches.

    A lot of this year's programme deals with AI in business software: what it actually gives us, and what it costs us. Both parts matter and both get discussed honestly. If you build business software for a living, this is your crowd.

    14-15 October, Park Inn at Alexanderplatz. Early-bird tickets are 800 EUR until this Friday, 31 July. After that they go up to 950 EUR.

    kandddinsky.com/

    #KanDDDinsky #DDD #DomainDrivenDesign #SystemsThinking

  21. 🧩 „ECST-Event“, „Domain Event“, „ECST“: diese Begriffe fallen in fast jeder DDD-Diskussion, und erstaunlich oft meint jede:r etwas anderes damit.

    Christian Stettler räumt auf: ECST ist keine Event-Art, sondern eine Eigenschaft. Ihr Gegenpol ist die Event Notification, nicht der Domain Event. Was oft „ECST-Event“ heißt, ist eigentlich ein Replication Event.

    📖 Jetzt lesen: innoq.com/de/blog/2026/06/was-

    #DomainDrivenDesign #DDD #Softwarearchitektur

  22. 🧩 „ECST-Event“, „Domain Event“, „ECST“: diese Begriffe fallen in fast jeder DDD-Diskussion, und erstaunlich oft meint jede:r etwas anderes damit.

    Christian Stettler räumt auf: ECST ist keine Event-Art, sondern eine Eigenschaft. Ihr Gegenpol ist die Event Notification, nicht der Domain Event. Was oft „ECST-Event“ heißt, ist eigentlich ein Replication Event.

    📖 Jetzt lesen: innoq.com/de/blog/2026/06/was-

    #DomainDrivenDesign #DDD #Softwarearchitektur

  23. 🧩 „ECST-Event“, „Domain Event“, „ECST“: diese Begriffe fallen in fast jeder DDD-Diskussion, und erstaunlich oft meint jede:r etwas anderes damit.

    Christian Stettler räumt auf: ECST ist keine Event-Art, sondern eine Eigenschaft. Ihr Gegenpol ist die Event Notification, nicht der Domain Event. Was oft „ECST-Event“ heißt, ist eigentlich ein Replication Event.

    📖 Jetzt lesen: innoq.com/de/blog/2026/06/was-

    #DomainDrivenDesign #DDD #Softwarearchitektur

  24. 🧩 „ECST-Event“, „Domain Event“, „ECST“: diese Begriffe fallen in fast jeder DDD-Diskussion, und erstaunlich oft meint jede:r etwas anderes damit.

    Christian Stettler räumt auf: ECST ist keine Event-Art, sondern eine Eigenschaft. Ihr Gegenpol ist die Event Notification, nicht der Domain Event. Was oft „ECST-Event“ heißt, ist eigentlich ein Replication Event.

    📖 Jetzt lesen: innoq.com/de/blog/2026/06/was-

    #DomainDrivenDesign #DDD #Softwarearchitektur

  25. 🧩 „ECST-Event“, „Domain Event“, „ECST“: diese Begriffe fallen in fast jeder DDD-Diskussion, und erstaunlich oft meint jede:r etwas anderes damit.

    Christian Stettler räumt auf: ECST ist keine Event-Art, sondern eine Eigenschaft. Ihr Gegenpol ist die Event Notification, nicht der Domain Event. Was oft „ECST-Event“ heißt, ist eigentlich ein Replication Event.

    📖 Jetzt lesen: innoq.com/de/blog/2026/06/was-

    #DomainDrivenDesign #DDD #Softwarearchitektur

  26. RE: mastodon.social/@RuthMalan/116

    I’ll be there! Not giving a talk, alas, but always up for chatting or maybe playing a board game? 🤔 😁

    #domaindrivendesign

  27. RE: mastodon.social/@RuthMalan/116

    I’ll be there! Not giving a talk, alas, but always up for chatting or maybe playing a board game? 🤔 😁

    #domaindrivendesign

  28. RE: mastodon.social/@RuthMalan/116

    I’ll be there! Not giving a talk, alas, but always up for chatting or maybe playing a board game? 🤔 😁

    #domaindrivendesign

  29. RE: mastodon.social/@RuthMalan/116

    I’ll be there! Not giving a talk, alas, but always up for chatting or maybe playing a board game? 🤔 😁

    #domaindrivendesign

  30. RE: mastodon.social/@RuthMalan/116

    I’ll be there! Not giving a talk, alas, but always up for chatting or maybe playing a board game? 🤔 😁

    #domaindrivendesign

  31. The conference is full steam, and Zsófia Herendi and I will have our hands-on in 3 days. If business value and org design are topics that matter to you, join us at "From org chart to designed organization: making the invisible visible with business models and teams" hands-on lab!

    Learn more here ➡️ 2026.dddeurope.com/program/fro

    #DDDEurope #TeamTopologies #DomainDrivenDesign #OrganizationalDesign

  32. The conference is full steam, and Zsófia Herendi and I will have our hands-on in 3 days. If business value and org design are topics that matter to you, join us at "From org chart to designed organization: making the invisible visible with business models and teams" hands-on lab!

    Learn more here ➡️ 2026.dddeurope.com/program/fro

    #DDDEurope #TeamTopologies #DomainDrivenDesign #OrganizationalDesign

  33. The conference is full steam, and Zsófia Herendi and I will have our hands-on in 3 days. If business value and org design are topics that matter to you, join us at "From org chart to designed organization: making the invisible visible with business models and teams" hands-on lab!

    Learn more here ➡️ 2026.dddeurope.com/program/fro

    #DDDEurope #TeamTopologies #DomainDrivenDesign #OrganizationalDesign

  34. The conference is full steam, and Zsófia Herendi and I will have our hands-on in 3 days. If business value and org design are topics that matter to you, join us at "From org chart to designed organization: making the invisible visible with business models and teams" hands-on lab!

    Learn more here ➡️ 2026.dddeurope.com/program/fro

    #DDDEurope #TeamTopologies #DomainDrivenDesign #OrganizationalDesign

  35. The conference is full steam, and Zsófia Herendi and I will have our hands-on in 3 days. If business value and org design are topics that matter to you, join us at "From org chart to designed organization: making the invisible visible with business models and teams" hands-on lab!

    Learn more here ➡️ 2026.dddeurope.com/program/fro

    #DDDEurope #TeamTopologies #DomainDrivenDesign #OrganizationalDesign

  36. Zsófia Herendi and I will be running a hands-on lab at DDD Europe in Antwerp on
    June 12.

    The premise: you can't design teams without understanding how the business
    creates value.

    We'll connect Business Model Canvas to Team Interaction Modeling. Practical
    heuristics that you will discover by working with your peers!

    This is not a slideshow. A lab where you will share insights with others!

    Use the link for a discount: ti.to/on3/aardling26/discount/

    #DDDEurope #TeamTopologies #DomainDrivenDesign

  37. Zsófia Herendi and I will be running a hands-on lab at DDD Europe in Antwerp on
    June 12.

    The premise: you can't design teams without understanding how the business
    creates value.

    We'll connect Business Model Canvas to Team Interaction Modeling. Practical
    heuristics that you will discover by working with your peers!

    This is not a slideshow. A lab where you will share insights with others!

    Use the link for a discount: ti.to/on3/aardling26/discount/

    #DDDEurope #TeamTopologies #DomainDrivenDesign

  38. Zsófia Herendi and I will be running a hands-on lab at DDD Europe in Antwerp on
    June 12.

    The premise: you can't design teams without understanding how the business
    creates value.

    We'll connect Business Model Canvas to Team Interaction Modeling. Practical
    heuristics that you will discover by working with your peers!

    This is not a slideshow. A lab where you will share insights with others!

    Use the link for a discount: ti.to/on3/aardling26/discount/

    #DDDEurope #TeamTopologies #DomainDrivenDesign

  39. Zsófia Herendi and I will be running a hands-on lab at DDD Europe in Antwerp on
    June 12.

    The premise: you can't design teams without understanding how the business
    creates value.

    We'll connect Business Model Canvas to Team Interaction Modeling. Practical
    heuristics that you will discover by working with your peers!

    This is not a slideshow. A lab where you will share insights with others!

    Use the link for a discount: ti.to/on3/aardling26/discount/

    #DDDEurope #TeamTopologies #DomainDrivenDesign

  40. Zsófia Herendi and I will be running a hands-on lab at DDD Europe in Antwerp on
    June 12.

    The premise: you can't design teams without understanding how the business
    creates value.

    We'll connect Business Model Canvas to Team Interaction Modeling. Practical
    heuristics that you will discover by working with your peers!

    This is not a slideshow. A lab where you will share insights with others!

    Use the link for a discount: ti.to/on3/aardling26/discount/

    #DDDEurope #TeamTopologies #DomainDrivenDesign

  41. The response to the #IDDD Tour has been tremendous! To accommodate the waitlist, #VaughnVernon has added a second date: June 15–18.

    Register here: kalele.io/training/iddd/
    $400 seats — $1,600 OFF

    #VaughnVernon #DDD #DomainDrivenDesign #EventStorming

  42. RE: mastodon.social/@venkats/11656

    I’m not only presenting two talks (one is a game, guess what it is), but also thrilled to do a workshop on my current passion: #EventSourcing and #DomainDrivenDesign #Java

  43. RE: mastodon.social/@venkats/11656

    I’m not only presenting two talks (one is a game, guess what it is), but also thrilled to do a workshop on my current passion: #EventSourcing and #DomainDrivenDesign #Java

  44. RE: mastodon.social/@venkats/11656

    I’m not only presenting two talks (one is a game, guess what it is), but also thrilled to do a workshop on my current passion: #EventSourcing and #DomainDrivenDesign #Java

  45. RE: mastodon.social/@venkats/11656

    I’m not only presenting two talks (one is a game, guess what it is), but also thrilled to do a workshop on my current passion: #EventSourcing and #DomainDrivenDesign #Java

  46. RE: mastodon.social/@venkats/11656

    I’m not only presenting two talks (one is a game, guess what it is), but also thrilled to do a workshop on my current passion: #EventSourcing and #DomainDrivenDesign #Java

  47. An alle #DDD und #BA und #RE Enthusiasten - das ist sicher etwas, was für alle interessant sein wird. Wie kann #DDD einer #LLM / #AI helfen, bessere Ergebnisse zu erzeugen? Genau das werden wir diskutieren!

    meetup.com/ddd-vienna/events/3 #domaindrivendesign

  48. An alle #DDD und #BA und #RE Enthusiasten - das ist sicher etwas, was für alle interessant sein wird. Wie kann #DDD einer #LLM / #AI helfen, bessere Ergebnisse zu erzeugen? Genau das werden wir diskutieren!

    meetup.com/ddd-vienna/events/3 #domaindrivendesign

  49. An alle und und Enthusiasten - das ist sicher etwas, was für alle interessant sein wird. Wie kann einer / helfen, bessere Ergebnisse zu erzeugen? Genau das werden wir diskutieren!

    meetup.com/ddd-vienna/events/3