EventModeling (@eventmodeling) 's Twitter Profile
EventModeling

@eventmodeling

Event Modeling describes systems for all roles in an organization: workflows, coupling & complexity for estimating, building, scaling, & maintaining.

ID: 1142620029050949634

linkhttp://EventModeling.org calendar_today23-06-2019 02:26:58

2,2K Tweet

5,5K Followers

5,5K Following

Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

You wouldn't hate stored procedures so much if you didn't have to maintain and author sql code. The behaviour-data separation is a dysfunction that was born decades ago and persists today. Break free from this & other dysfunctions in one step by #EventSourcing & EventModeling

Ryan Singer (@rjs) 's Twitter Profile Photo

First impressions using tldraw for breadboarding, now that they've added elbow arrows. So far, loving it. And excited by the potential of baking some conventions in because it's an SDK. (For those who know breadboarding and are curious about the additional colors and boxes ...

Ryan Singer (@rjs) 's Twitter Profile Photo

Hat tip to Adam Dymitruk because his Event Modeling inspired some of these new conventions. I'm finding the`read model` and `command` conventions translate naturally to breadboards. There are very interesting differences between the EM and breadboarding style of describing a

Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

Practice makes perfect is BS. Practice makes PERMANENT. And we've been practicing CRUD, TDD, Agile and many other dysfunctional stuff that keeps us in a death spiral in systems automation. Practice EventModeling and #EventSourcing. Get good at THAT.

Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

Event Modeling is future proof. #AI did not disrupt it. Since automation was built into the methodology from the start, agents can be described as either users or specific processors. You can combine that to show how a multi-agent system would work without throwing away your

Event Modeling is future proof. #AI did not disrupt it. Since automation was built into the methodology from the start, agents can be described as either users or specific processors. You can combine that to show how a multi-agent system would work without throwing away your
Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

At the heart of the transaction where we can use EventModeling to show non-technical people where #EventSourcing enforces a concurrency strategy in a system.

Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

DHH Do estimates and back then up with fixed costs and free bug fixes for life. Ryan Singer has commented on EventModeling as part of the framing in Shape Up. He presented this at the #EventModeling conference in Vancouver last year. We've worked this way for every project for years.

Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

Level of effort has to be deconstructed into unique steps of state change and unique state projections to accomplish the goal. EventModeling is the clearest way to do this while embracing human-friendly notation and mechanics such as "specification by example".

Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

The idea of a "Consistency Map" is the reworking of referential integrity from the ground up with more complete goals. Referential integrity is just a paper map; we need driving directions. A Consistent Map shows how optimistic and pessimistic consistency rules fit together. You

The idea of a "Consistency Map" is the reworking of referential integrity from the ground up with more complete goals. Referential integrity is just a paper map; we need driving directions. A Consistent Map shows how optimistic and pessimistic consistency rules fit together. You
Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

Karl Mehta Blaize D'souza ❤️ Because they're not using EventModeling. As AI matures (at least the LLM kind) you need structure that gives exact context. The 5% are setting the example. You could say the same thing about email adoption in the early 90s.

Alex Kobyshcha (@kobasad) 's Twitter Profile Photo

Ben Ford Adam Dymitruk EventModeling I'd speculate that it's because of a simple notation and high repetitiveness: only a handful of primitives and four patterns. And it's natural language-based, which, I guess, plays especially well with LLMs.

Leanpub (@leanpub) 's Twitter Profile Photo

Understanding Eventsourcing: Planning and Implementing scalable Systems with Eventmodeling and Eventsourcing by Martin Dilger M Dilger is the featured book on the Leanpub homepage! #SoftwareEngineering #EventDrivenArchitecture #SoftwareArchitecture #Software #DistributedSystems

Understanding Eventsourcing: Planning and Implementing scalable Systems with Eventmodeling and Eventsourcing by Martin Dilger <a href="/dilgerma/">M Dilger</a> is the featured book on the Leanpub homepage! #SoftwareEngineering #EventDrivenArchitecture #SoftwareArchitecture #Software #DistributedSystems
Michael Dominick (@dominucco) 's Twitter Profile Photo

Had a great time hosting Adam Dymitruk Coder Radio! We broke down the essential concepts of Event Modeling and how it can change the way you think about software development. Check it out! 🔥 #EventModeling #SoftwareDevelopment Coder Radio coder.show/627

Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

On September 5th 2015 I set out to create a company where we could all work in the best way possible. #EventSourcing for everything, no meetings, no management hierarchy, open source everywhere - nothing that we knew was wrong in the industry would be present. It was a fork in

On September 5th 2015 I set out to create a company where we could all work in the best way possible. #EventSourcing for everything, no meetings, no management hierarchy, open source everywhere - nothing that we knew was wrong in the industry would be present. It was a fork in
Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

Why regular projects hit a crippling cost curve: too much coupling from the good intentions of reuse of previous work. Why we don't suffer this in EventModeling: We build to the side, not on top. The only coupling we accept is through the facts that happened in the past. It's

Why regular projects hit a crippling cost curve: too much coupling from the good intentions of reuse of previous work. 

Why we don't suffer this in <a href="/EventModeling/">EventModeling</a>: We build to the side, not on top. The only coupling we accept is through the facts that happened in the past.

It's
Adam Dymitruk (@adymitruk) 's Twitter Profile Photo

I couldn't think of a more deserving person to receive the community award than Martin Dilger ! Thank you to Allard Buijze and the rest of the wonderful people at AxonIQ for taking the time to recognize Martin's amazing dedication, discipline and willingness to help countless

I couldn't think of a more deserving person to receive the community award than Martin Dilger ! Thank you to <a href="/allardbz/">Allard Buijze</a> and the rest of the wonderful people at <a href="/axon_iq/">AxonIQ</a> for taking the time to recognize Martin's amazing dedication, discipline and willingness to help countless