Episode 19 - Vibe Modeling, Event Models for the C-Suite
April 23, 2025
Show Notes
In this episode of the Event Modeling and Event Sourcing Podcast, hosts Adam and Martin discuss the growth of event modeling and event sourcing, the launch of an online course, and upcoming workshops. They delve into the new trend of vibe coding, its implications for software development, and the concept of vibe modeling as a collaborative approach to system design. The conversation also touches on the challenges of managing large event models and the importance of maintaining readability and navigability in modeling tools. In this conversation, Adam Dymitruk and Martin discuss the intricacies of event modeling, focusing on workflows, the lifecycle of slices, and the importance of effective communication with C-level executives. They explore how to manage development processes, integrate UI and backend work, and the significance of having a clear definition of ready for slices. The discussion emphasizes the need for high-level overviews for executives and the importance of demos in showcasing completed work.
Takeaways
Event modeling and event sourcing are gaining traction in the industry.
The online course complements the book and enhances learning.
Vibe coding allows non-developers to create applications but poses risks.
Understanding the underlying concepts is crucial for effective coding.
Vibe modeling can enhance collaboration among stakeholders.
Event models should be manageable and navigable for clarity.
Miro has improved its performance for large event models.
Splitting event models can lead to usability issues.
The future of coding may involve more modeling and less traditional programming.
Event modeling provides a structured approach to system design. You want to have a listing of workflows in each section.
A lot of workflows are trivially short, so it makes sense to combine them.
The event model can serve as a living document that stays in sync with production.
Slices are self-contained pieces of work that support a workflow.
The lifecycle of a slice is often tied to a larger goal.
It’s important to have a demo of the slice to show its functionality.
Feature toggles can be used to manage unfinished code in production.
The definition of ready for a slice is crucial for client approval.
Developers can barter slices among themselves to manage workloads.
C-level executives need high-level overviews, not detailed event models.
Chapters
00:00 Introduction and Weather Banter
03:09 Event Modeling and Event Sourcing Growth
06:12 Course Launch and Learning Resources
09:24 Book Updates and Future Chapters
12:08 Vibe Coding: A New Trend
24:13 Vibe Modeling: The Next Evolution
24:53 Defining Goals and Vision in Application Development
27:27 The Importance of Event Modeling
29:21 Splitting Event Models: To Split or Not to Split?
32:46 Scalability of Event Modeling in Fintech
40:56 Maintaining Event Models: Keeping Them in Sync
41:57 Understanding the Life Cycle of a Slice
55:39 Navigating Agile Challenges
58:13 The Importance of UI in Slices
01:01:12 Team Collaboration and Skill Sharing
01:05:01 Eliminating Subjectivity in Development
01:07:25 Empowering Junior Developers
01:10:40 Integrating AI in Development
01:13:01 Communicating with C-Level Executives
01:22:59 New Chapter