EventModeling
@EventModeling
Followers
6K
Following
7K
Media
116
Statuses
2K
Event Modeling describes systems for all roles in an organization: workflows, coupling & complexity for estimating, building, scaling, & maintaining.
Joined June 2019
There's no better way to move projects forward than with true collaboration.
1
38
160
🚀 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: https://t.co/XxHCShKcid
0
3
4
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
2
1
4
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
1
2
8
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
2
4
12
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
7
9
67
We hear the same about @EventModeling
From a customer: "Every time we decided not to use #eventsourcing for a particular feature or component, we later regretted the decision and wished they had applied consistent patterns throughout."
0
2
7
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
0
3
7
@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.
1
2
4
This is how I feel about every slice in @EventModeling. We're part of the 5% where AI is a clear productivity enhancement.
What if I told you AI wrote it all? AI is getting interesting, this morning my task was to integrate the W5500 Eth wiz. I added in the SPI driver to Vivado, then created a new blank Vitis workspace and project to test out just the ethernet application. On a whim I asked
1
2
14
@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.
0
3
3
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
1
2
6
@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.
0
2
2
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".
Ron Jeffries apologized for inventing Story Points. He then went to call the whole idea of software estimation "evil." Story points is the Emperor's New Clothes. Everyone I've seen—and I mean everyone—uses points as a measure of time: 1 point = 2 hours 3 points = 1 day 5
0
3
6
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.
Lock Free Circular Buffer in C with Atomic Assembly: Build a thread-safe circular buffer using x86 cmpxchg in C. Perfect for kernel & real-time concurrency.
1
1
6
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
2
6
29
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.
0
2
8
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 ...
@steveruizok @tldraw First impression, I was worried about not being able to customize the route. Then I gave it a shot with a real project, and was surprised that 90% of the time, the elbows routed themselves reasonably. The most I needed to do was to choose a different magnet sometimes (north,
3
4
48