Virtual Domain-Driven Design

Nobody wanted to work with one team, and nobody would say it aloud. Yves Hanoulle cleared a room, banned talking, and let forty people silently self-select into three new teams. Read, watch, or listen: buff.ly/1j5fGNy

Everyone agreed on the standard, wrote the ADRs — and still nobody adopted it, not even the authors. @wouterla.bsky.social and @suzyla.bsky.social share why consensus can quietly erase ownership. Read, watch, or listen: buff.ly/2jn1f33

Nobody attends the community of practice nobody asked for—until someone makes people feel like they matter. @suzyla.bsky.social and @wouterla.bsky.social shared this story. Read, watch, or listen: buff.ly/WSmcowb

Getting from domain talk to a "good" model often stalls without domain experts reading code. Marco Schneider and Martin Günther shared a sticky-note technique for hearing sum and product types hiding in plain sentences. Watch it: buff.ly/5pagHCI

Why do good products slowly get worse even when teams keep shipping? @annemariecharrett.com walked us through the enshittification trap and how systems thinking catches quality… Watch or listen: buff.ly/W3ONE7E

Splitting teams along tech layers instead of business capabilities breeds handoffs, delays, and finger-pointing. One week out: @trond.hjorteland.com joins to diagnose these dysfunctions live. Register: buff.ly/xzyFsYJ

One person's holiday laptop full of scripts turned into 200 "custom" reports (really 5 templates in disguise). @kathrynhempstalk shared how getting data out was never designed for — and cost… Read, watch, or listen: buff.ly/Xl58fZe

One week out: Marco Schneider and Martin Günther explore how linguistic cues can surface types collaboratively, before the model calcifies, rather than being bolted on after the fact. Register: buff.ly/xfbsKCb

Good ideas in software delivery often sound wrong at first, which is why teams reject them before giving them a chance. Hibri's session explored why our intuition misleads us so… Watch: buff.ly/0wvhkbO

Anyone who has run a workshop that mattered knows the room is the easy part. Read, listen or watch Katie Clark's full story here: virtualddd.com/facilitating...

Translating concepts across bounded contexts often gets messy fast, meaning lost nuance. We dug into this with @indu-alagarsamy.bsky.social, @julielerman.bsky.social, @nick-tune.me and @bitboss.bsky.social. Watch or listen: buff.ly/wJ4ovzc

Told she needed grey hair to be taken seriously as a facilitator, Katie Clark leaned into it instead of fighting it. Real workshop prep happens in corridors, not rooms. She shared this story. Read, watch, or listen: buff.ly/Z5eaxJK

Context mapping often stays a static diagram nobody revisits once the workshop ends. @ziobrando.bsky.social pushed the idea further, exploring how to keep it living and useful as teams and systems evolve. Watch: buff.ly/YIIFqhF

We often assume that once a team has a diagram, they have a shared understanding. It's only when someone starts asking basic questions that the diagram starts to fall apart. Read, Listen or Watch more of @vanessaformicola.bsky.social her story: buff.ly/aOIQ7uj

Getting from domain talk to a "good" model is hard—DDD's patterns show the destination, not the journey, especially with experts who can't read code. Marco Schneider and Martin Günther share a… Get info & RSVP: buff.ly/csI1ZY2

Cloud unreachable, warehouses dark, thousands of orders mid-fulfillment: what keeps logistics running when a national blackout hits? Emilio Carrión shared how offline-first architecture and post-outage reconciliation kept Mercadona Online alive… Listen as a podcast: buff.ly/fsG3Dqn

Modelling a domain in code often drifts from the actual business logic. This hands-on session dug into functional domain modelling in practice, keeping types and behaviour honest. Watch: buff.ly/hOvWEbC

Our new DDD starting point is an EventStorming timeline, so it ends in two empty stickies. Step three and beyond are not written yet, because we need to design that together. buff.ly/0btwtGn

Broken things at work keep breaking, and we rarely have the language for why. @trond.hjorteland.com introduces Open Systems Theory, then we diagnose real dysfunctions live, together. Get info & RSVP: buff.ly/H580ohp

Four "services" drawn as separate boxes, but one tangled codebase underneath, in a medical product nobody could safely change. @vanessaformicola.bsky.social shared how naming what a team actually owns… Read, watch, or listen: buff.ly/5JB3t8z

Step one of any DDD learning journey should be: find out whether this is even your problem. Step two: learn the four words that matter. What resources would you add to those first two steps? buff.ly/0btwtGn

Most decisions in software teams don't fail because people disagreed. They fail because people thought they agreed, but they didn't, and nobody found out until much later. virtualddd.com/facilitating...

AI drafts, suggests and helps us build. What it does not do is decide what we think. The thinking, the opinions and the mistakes are ours. buff.ly/0voDv53

When the network vanishes, most systems just stop working. One week out: Emilio Carrión joins us to talk offline-first architecture and surviving a national blackout. Register: virtualddd.com/sessions/sur...

There is a version of career progression that looks like success from the outside and feels like a slow erosion from the inside. You attend more meetings, write less software, and someone asks if you'd like to become an architect. Read, Listen or Watch the full story by Larissa here: buff.ly/99BtmNJ

Two people can leave a meeting feeling aligned and actually disagree — you just won't find out until weeks later. Michael shared a great story about a whiteboard moment where writing down someone's words surprised even them. Read, watch, or listen: virtualddd.com/facilitating...

There's a pattern that turns up in almost every struggling team. The problem gets named as a technical one, the technical fix gets applied, and nothing actually improves. Listen, watch or read about @mathiasverraes.bsky.social and many more of our @dddeu.bsky.social special stories! buff.ly/lWZiNoX

We design for high availability assuming the cloud is always reachable. What happens when a nationwide blackout cuts warehouses off completely? Emilio Carrión shares how Mercadona Online kept fulfilling orders anyway. Get info & RSVP: virtualddd.com/sessions/sur...

There's a certain frustration that comes from doing everything right, by the book, and still watching it fail. Not because the methods were wrong, but because the real problem was somewhere else entirely. Watch, Listen and Read @heimeshoff.bsky.social his full story: buff.ly/6bJ9wv4

Architects often start enthusiastic and end up worn down by the gap between vision and what systems allow. Larisa Feldman spent years watching this happen before reluctantly stepping into the role herself. Read, watch, or listen: buff.ly/wg1Inqg

It's hard when teams identify problems as technical, but the real issues are deeper. We interviewed nine practicioners at @dddeu.bsky.social and ask them: what's the hardest part of facilitating software architecture and design? Read, watch, or listen: buff.ly/urFrFzD

We've all been in that meeting. Someone senior has already decided on a solution — maybe they read something, maybe a vendor pitched it to them — and now the conversation isn't really about the problem anymore. Read, Watch, Listen to Kim who shares how he dealt with this situation: buff.ly/xJVD0Hv

It's tough when clients already have "the answer" before understanding the problem. Kim Kao shared how he redirected a client focused on Kubernetes to map their business impact first. Read, watch, or listen: virtualddd.com/facilitating...

When methods fail due to cultural resistance, not technique. @heimeshoff.bsky.social shares his story where feedback felt like violence & leadership gave a quiet "no." Read, watch, or listen: buff.ly/1ANfd4z

If someone brings up an alternative and you're like oh no, that's a horrible idea think about okay what assumptions may this person be making that are not being clarified. Listen, Read or Watch to @noctovis.bsky.social explaining how this and more can make for better conversations: buff.ly/F8qaXIw

It's hard to get consensus when everyone has an opinion but no one agrees on the problem. @noctovis shares how to shift from arguments to effective collaboration. Read, watch, or listen: virtualddd.com/facilitating...

There are many architecture workshops that help you figure out which bite-sized microservices you should extract from monoliths. But with everything else, you need to understand what it is you're working with before you start working with it. Check Aino Vonge Corry full story here: buff.ly/PQOgn3z

It's easy to miss the big picture when deep in domain details. @trond.hjorteland.com talk explored how to connect local models to the larger system strategy, helping us 'see the forest for the trees.' Watch or listen: buff.ly/kLLYT6k

It's hard when architects assume they share a system's structure. Aino (Cornils) Vonge Corry shared a story about asking a team to draw their monolith & realizing everyone saw something different. Read, watch, or listen: buff.ly/PQOgn3z

There's no such thing as a one-size-fits-all methodology like Agile, Scrum, Lean, or Six Sigma. It doesn't matter whether you're talking about project management or financing a system. Read, Watch or listen to the full story from Simon Wardley here: buff.ly/Etr9aHT

Building psychological safety in remote teams can feel elusive. @nativewired.com led a debate on how to foster it effectively. Watch or listen: buff.ly/1KnVfI3

Discussion will be led by @trond.hjorteland.com . You might know Trond Hjorteland from his talks on sociotechnical and open systems at conferences like DDDEU, and this one, hosted by @virtualddd.com www.youtube.com/watch?v=_B7A...

It's hard when method wars obscure the actual challenge. @swardley.bsky.social shared how mapping a system first avoids this trap & leads to success. Read, watch, or listen: buff.ly/kzK76iV

The fact that you as an individual can make a mistake, indicates that there's some kind of systematic flaw on the system. Watch, listen or read the full story from @lizthegrey.com here: buff.ly/TvVOw2m

Ensuring projections clearly express domain intent can be tough. This talk with @mathiasverraes.bsky.social and @ericevans0.bsky.social explored live coding techniques to craft more expressive projections. Watch: buff.ly/fTX4V1I

It's tough when a major outage demands centralized control, but the true fix comes from an unexpected place. @lizthegrey.com shared a story where psychological safety allowed an engineer to surface the solution. Read, watch, or listen: buff.ly/e05CGau