It's been 8 years since I started Adaptech Group. We're about to open another office in Quebec! What a great feeling being able to help so many clients and free them from the dysfunction of the software industry. They are ready for an incredible future!

Our clients:

- don't lose any data
- keep their costs constant as they add features
- actively collaborate across their entire organization
- slash their overhead in tooling, management and process
- have solutions built to scale with increased demand
- are not vendor-locked
- are leveraging open source to keep costs down
- and many, many more advantages

Our unique approach using the combination of #EventModeling and #EventSourcing is about to take off with what #AI is providing. I'm so happy that everyone that saw the light and believed in our approach - you're about to tap the benefits of building the right way.

Thank you to Nicolas, Jonathan and everyone that joined since. Here's to another 8 years!

All this talk about measuring developer productivity is still going on. I didn't bother commenting on it because we solved that problem years ago. We switched to fixed costs per slice. It's one of the many problems that #eventmodeling solved.

#AI is revolutionizing the way we work, making us faster and more efficient. However, if we continue to use outdated or ineffective approaches, we risk falling behind by entrenching ourselves as experts in irrelevant practices - AI will make us good blacksmiths in a world that's adopting cars. Without a clear strategy for automating our systems, AI can only make us faster at being average.

#EventModeling comes in at this point - it provides the perfect level of depth to define the "how" without getting lost in the details. Don't let AI go to waste - find the sweet spot for expressing your goals and leverage it to boost your productivity. Your competition is already doing that; make sure you do it better - and there no way better than with Event Modeling. This is how it will play out for the rest:

I've finally migrated the #EventModeling community away from #Slack and onto #Discord. You can join it here: https://discord.gg/tHYA6943wx

Back in 2009 I was doing nothing but #eventsourcing and some of the biggest names in the community and open source were ridiculing me publically. Those same people are trying to sell me their event sourcing frameworks today after running out of ideas on ways to avoid event sourcing and bring the same benefits.

I see the same thing happening with #EventModeling. It's funny to see effort on the different takes on modeling (including trying to add UX and UI and example data) and effort used to avoid mentioning EM.

I'm happy that I now have a company #adaptechgroup full of experts on these key ways of automating systems. It took a long time and a lot of effort to get here.

@flooper this is why I made #EventModeling

@notroot we run our systems like accounting and look after insurance companies, shipping logistics and trading platforms. It can't think but it's much better than the average junior developer. GPT4 has made us at least twice as efficient. We only deal with Event Sourcing so there is little room for being too creative outside of what we design for information flow in #EventModeling. The amount of automation from transcripts of requirements meetings that end up with a system diagram through AI is priceless. Conversation -> EM diagram -> code. And you can jump in at any point or reverse. It's incredible.

One of the best things we stopped doing with our clients is designing #dddesign aggregates with them - that is something devs can use if at all. The effort is better used in overall information flow through the system by example. It's how #EventModeling eliminates waste.

same goes for Sagas.

One of the most overlooked things in this industry is what you DON'T do to get the best productivity and quality in the SDLC.

As I reflect on #eventsourcing projects of the past 15 years - especially those implemented by others, I see that we have a team that avoids all the mistakes learned in the infrastructure part of the implementation. We have way more than than 10,000 hours of flight time.

Some of the mistakes:

Coupled read models. No time taken to do #EventModeling. Middleware and tooling bloat. Cloud infatuation. Distracted by saga and processor design. Event and command handlers that are not pure functions. Optimizing for performance at the start of a project with no evidence for the need to do so. Over-reliance on the aggregate concept from #dddesign. Not thinking of "closing of the books" and relying on replaying the entire event history to upgrade pieces of the solution. Over-thinking schema design instead of relying on versioning of events...

...just to name a few 😄

#FModel aims to bring functional, algebraic, and reactive domain modeling to #Kotlin. Check out the new demo application 💙https://github.com/fraktalio/fmodel-ktor-demo💙 #Ktor #R2DBC #EventSourcing #CQRS #EventModeling

@nurkiewicz oh wow. Thank you for all of that. Now I need to pick what's best for the style of diagram that #EventModeling is. Something that already does wireframes and story boards would be helpful.

I'm going to be including #EventModeling diagrams with some #opensource projects. What tool and format should the EM diagrams be authored in?

We showcase our capabilities through well-documented, production-ready demos. These demos serve as living examples of our vision and demonstrate the value we bring to the table. They allow you to witness firsthand how our models and solutions can optimize processes, maximize efficiency, and unlock new opportunities for growth. https://github.com/fraktalio/order-demo #AxonFramework #EventSourcing #EventModeling #CQRS #SoftwareDesign

The success that #EventModeling and #eventsourcing enable is incredible. Please feel free to share this with others if they are not convinced that they can improve their projects this way. Thank you to Jason, Fran and others at ShedSuite for an incredible journey together!

@carlfranklin any interest in covering #EventModeling on the dot net rocks show?

There's a new testimonial on the adaptechgroup.com site. If you're considering collaborative design techniques like #EventModeling along with #EventDriven development, including #EventSourcing, have a look to see how we worked with Jason Graber and his team at Shed Suite to attain incredible results.

If you are doing #EventModeling and want to get verified, let me know!

Why does #EventModeling matter?

Agilists try to confuse people into thinking R&D (where you trial & error a lot and iterate) is engineering. It's only a part of engineering in the initial phase. #Engineering is working from the resulting blueprints and schematics to build in a reliable and predictable manner. #Agile software development is NOT engineering.

If you're new to this concept, go to EventModeling.org to read more.

#Research #Development #SDLC

A new #Fmodel demo application has been published https://github.com/fraktalio/fmodel-spring-state-stored-demo. It is a traditional/state-stored system/flavor. You can have both, event-sourced and/or state-stored. We make the transition from one to another simple and easy! Check our reference guide for more https://fraktalio.com/fmodel/ #EventModeling #DomainModeling #Kotlin

Time for an in-person workshop! If you want to learn #EventModeling #EventSourcing and #CQRS from 100s of successful projects, join me in New York in April! I'll be joined by Chris and Alexandra. I hope to see you there in person!

https://adaptechgroup.com/workshops/#