Welcome to the ThoughtWorks podcast.

This is Neil Ford.

And I'm Jermak De Haini.

And we're here at the tab face-to-face meeting.

And as often happens, we have interesting discussions that come up as we're face-to-face.

So this morning, we're joined by a couple of the Doppler members that put

together the technology radar. Eric Donberg, the head of technology in Germany. And Evan Boucher,

a tech lead from Melbourne, Australia. And we're going to talk about a topic this morning about

serendipitous events. So Zabak. We are seeing this emerging trend around the idea of exposing events, particularly business

domain events, before knowing who the consumers are or what the specific applications

are and hoping for discovery of those events by other people in the

organizations and creation of the value using those events without us directly orchestrating

it. And I can imagine that this can be quite heated discussion because it sounds like

things that we don't want to do, like creating big upfront architecture. But I want to

open the discussion with perhaps giving some examples of seeing this theme in the organization

and look at the pros and cons of it. To give an example, a small example of that we have seen

within Fowards is the events that

are identifying submission of timesheets.

So we all put our time allocated for different projects at the end of the week.

And the system that's capturing that has decided, or the team has decided to expose these events that timeships have been

submitted. And the following effect of that has been that other teams have found value in that

and they created other applications consuming those events, such as calculating the leave that

...