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

Learn DDD — Virtual DDD

Free resources for learning Domain-Driven Design, curated by the Virtual DDD community: a reading list, the ddd-crew tools, and heuristics taken from real sessions.

virtualddd.com

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

Organisational Dysfunctions and Open Systems Theory

Most teams can list what is broken at work but lack a language for why it keeps recurring. Trond Hjorteland diagnoses real dysfunctions using Open Systems…

virtualddd.com

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

Social Decision Records: The Other Half of Architecture

Social decision records apply ADR rigour to people decisions. Learn how Vanessa Formicola built team ownership before refactoring four tangled services.

buff.ly

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

Learn DDD — Virtual DDD

Free resources for learning Domain-Driven Design, curated by the Virtual DDD community: a reading list, the ddd-crew tools, and heuristics taken from real sessions.

buff.ly

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

AI usage on this site — Virtual DDD

Where AI is used on this site and where it is not: the recordings, the writing, the images, and the site itself.

buff.ly

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...

People are reaching for DDD again, twenty-odd years after Evans wrote it down. So are we, after a fashion. virtualddd.com has been rebuilt from the ground up, and the timing isn't entirely a coincidence.

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

The Reluctant Architect: A Career Path Nobody Plans

Larisa Feldman spent years watching architects lose their spark—then became a reluctant architect herself. On why good architecture serves engineers.

buff.ly

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

When the Problem Isn't Technical: 9 Voices from DDD Europe

At DDD Europe, nine practitioners agreed the problem isn't technical. Discover why facilitation, power structures, and the right people decide outcomes.

buff.ly

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

Cultural Resistance to Collaborative Modeling

Why EventStorming and collaborative modeling fail against cultural resistance — and why a real mandate matters more than the right method.

buff.ly

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

See the Forest for the Trees - Trond Hjorteland

When developing your software products, be it coding, testing, user experience, product management, or all the other elements required to solve a customer need, do you understand what the rest of the…

buff.ly

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

Why Drawing the Same System Reveals Different Architectures

What happens when architects draw the same system and get different diagrams? Learn how externalising mental models transforms architecture discussions and reveals hidden disagreements.

buff.ly

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

Psychologic safety in remote collaboration with Gitte Klitgaard

The recent COVID-19 pandemic forced us DDD practitioners to move our collaborative modelling efforts to the remote world. Within collaborative modelling, we want to share all the information we have,…

buff.ly

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...

See the Forest for the Trees - Trond Hjorteland

YouTube video by Virtual Domain-Driven Design

youtube.com

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

Why Method Wars Hide the Real Architecture Problem

Simon Wardley shares how mapping component evolution resolved methodology wars on HS2. Discover why understanding context matters more than choosing the right method.

buff.ly

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

[DDDDD-20] Live coding: Expressive Projections

Let’s write some event sourced projections! Our weapons of choice include higher order functions, algebraic data types, pattern matching, all the goodies of a modern programming languages. But the…

buff.ly

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

Staying Out of the Way: Incident Command & Psychological Safety

When a Google Cloud outage was fixed by someone no one paged, the real lesson was psychological safety. Learn how Liz Fong-Jones built resilient teams.

buff.ly