I might even try example mapping too, but I will have to do some more reading and trials for that

Overall, I don't regret the workshop because it brought some good energies into the collaboration and also gave me, as a newcomer in the company, a ton of insight. And I will try to keep further workshops more focused on a single configuration, which hopefully will give us more in-depth timelines.

I decided to go with event storming because I didn’t have any experience with example mapping, and to be honest, from the description in the book, it was not obvious to me for how to apply it to my situation.

This meant that initially we were not able to even establish a timeline and instead had a big chaos on our hands, which we later drastically simplified, and then the simple timeline emerged

I wanted to give you some feedback for your very generous advice. You were of course completely right that the final storyline was indeed pretty simple, and the complexity was in different configurations and in the details.

I will check out Example Mapping

I still think there might be value to agree on the global storyline. Especially because we have Hardware, Firmware, Middleware, Data Science teams involved - so there might be misunderstandings.

Thanks for the input!

I was planning to use EventStorming but the argument for the "simplicity" of the story makes a lot of sense, events like "Measured trace delivered" are simple but how they come to be is not (physics and stuff).

Any chapters in your book you would recommend as preparation for a workshop of this kind?

What about a thin interface for unit testing?

I do not have the perfect arguments that a more collaborative way of working is more productive but I for sure know that I enjoy it more.

For sure the developers were already used to working in isolation, enhanced by massive month-long tickets and knowledge silos.

My tries of pulling people into calls for clarifications, reviews or design were met with question marks and resistance so I gave up.

assuming I am a nerd about architecture but also have the need for some practicality, how relevant is the course?

I did a little survey back in January with dismal results (maybe bad phrasing?)

Fascinating counter point is the Anthropic team which seems to pair program: x.com/lucca_dev/st...

My hypothesis is that in-person collab is often invisible which is why many of the people I questioned don't recognize it as such.

But I am honestly still confused if my expectations of actual pairing-style team-work are out snyc with most teams or if I haven't asked enough people.