EventModeling

There's no better way to move projects forward than with true collaboration.

Funny how people that got dragged kicking and screaming into #EventSourcing are now event sourcing experts. Watch as these same people are getting dragged kicking and screaming into DCB. Can't wait for the new experts to start telling me how to do what I've been teaching for 6+ years. Oh and before they switched and became experts, they publically shamed me about these subjects - only to erase that part of it out of their recollection. Now there are @EventModeling "improvements". Brings to mind a famous quote about eggs and grandmas.

@dhh @Beelinkofficial @opencode @ryanrhughes Then reign in context with Ralph loops on @EventModeling workflows and GWTs per slice, based on #EventSourcing for state. We can do this on last year's LLMs. youtu.be/HJ63_wIrCQI?si…

@adymitruk @EventModeling Fantastic!… to add to your favorite word “code” and for all German speaking folks… I had the pleasure to speak to Martin Dilger about #Eventsourcing and #Eventmodeling on the @byndcodepodcast x.com/byndcodepodcas…

A year of podcasts with Martin Dilger! So much fun discussing @EventModeling and #EventSourcing! ummm... podcast.eventmodeling.org

Love working with @openclaw . It's doing @EventModeling for me.

🚀 5 days left! Tired of every code change breaking something? Learn how to design predictable systems, modernize legacy code, and even stop AI hallucinations. Intro Workshop on Event Modeling & Event Sourcing — Dec 9, 8am PST. 👉 Seats limited: #Workshops" target="_blank" rel="nofollow noopener">adaptechgroup.com/#Workshops #eventmodeling #eventsourcing

Anyone thinking that the #AI bubble is about to pop is badly mistaken. We're where most companies aren't even at this stage of html adoption during the beginning of the dotcom boom. We have barely started to understand how to use it effectively. We don't know in which sectors the largest tailwind benefits will fall. And we have no standards for communicating our requirements. That's why I'm betting on @EventModeling to be that language.

I couldn't think of a more deserving person to receive the community award than Martin Dilger ! Thank you to @allardbz and the rest of the wonderful people at @axon_iq for taking the time to recognize Martin's amazing dedication, discipline and willingness to help countless people to understand and use @EventModeling and #EventSourcing! Here is Martin's reaction, if you're not following him yet, make sure you do! lnkd.in/g4tDNTcG

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 we can deliver on fixed costs and fix bugs for free. See the work we've been doing at @adaptechgroup for over a decade.

Understanding Eventsourcing: Planning and Implementing scalable Systems with Eventmodeling and Eventsourcing by Martin Dilger @dilgerma is the featured book on the Leanpub homepage! #SoftwareEngineering #EventDrivenArchitecture #SoftwareArchitecture #Software #DistributedSystems #books #ebooks The first book to combine Eventmodeling & Eventsourcing to plan software systems of any size and complexity. Find it on Leanpub!

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 the road for me, if this didn't work, I would stop trying and just plan for my retirement as I bounce from different employers and gigs until I had enough in the bank. But nothing prepared me to how successful this self-imposed ultimatum would be! We've had no turn-over in that time because of the vision and environment. We developed #EventModeling as a core way to eliminate all that waste as we set out to do. Sure we needed to accommodate our clients and include some of their processes to work with them, but at the core, we achieved and proved that dropping nearly all that is considered "best practices" in the industry allowed us to get to another level that is unimaginable to those that are not fully involved and are sitting on the side-lines critiquing our ambitions. Years ago, I thought this would be a major milestone - and it is! - but when we realise how much more we can do with this as the foundation for the next 10 years, I didn't bother to make a large party or celebration. This is a thank you to all those that believed in us at @adaptechgroup and at our clients'. I would rather continue to celebrate at each of the steps as we continue into the future. So what does that involve? Well we know that there is Event Modeling tooling around the corner and I'm gathering investors for that as well as putting my own money behind it. There is the Event Modeling book that will be out this year - and I'm glad I waited! There is so much more to share now. Again thank you for all those that directly or indirectly supported me and our dedicated people at Adaptech, it wouldn't be fair to list names here but you know who you are and I love you all. We found the best way to automate information systems. Here is to the next 10 years which will be even more amazing! ❤️

We hear the same about @EventModeling

Had a great time hosting @adymitruk 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 @CoderRadioShow coder.show/627

@commandodev @adymitruk @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.

This is how I feel about every slice in @EventModeling. We're part of the 5% where AI is a clear productivity enhancement.

@karlmehta @blaizedsouza 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.

@monkeyonahill @adymitruk Most likely

@adymitruk @EventModeling who are you publishing it with? leanpub?

The @EventModeling book will be written this year. I'm glad I didn't write it earlier as there have been so many incredible insights since 2019 when I initially thought it would be needed. Instead, we worked with the community and clients directly on applying it. Now with the feedback and data, a much better book will be available.

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 want this map to be as small as possible - only containing actual business rules. It is a DAG like in #git; @EventModeling ensures we don't encode circular references. This is a much more important concept than event schemas in distributed #EventDriven systems where everyone leaves out temporal aspects of dependencies. With this map we don't over-engineer by relying on technical constructs like correlation and causation IDs embedded in metadata - yes, it should feel dirty to use those in your business logic. And yes, you should throw out your enterprise patterns books out; they're build walls between business and tech this way. Those concepts, if important, don't belong in metadata. Instead, we should walk actual data points that the workflows use. AND "old data" is no longer a mystery reason for why a precondition exists or how it manifested; #EventSourcing is REQUIRED for explicitly enforcing business rules properly; state is not enough. To really get there, we need to write our own indexes, collaboratively. RDBMS and current-state-only data management buries these concepts far from a collaborative level for tech and business sides.

@dhh Do estimates and back then up with fixed costs and free bug fixes for life. @rjs 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.

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