Today's stream starts at 20:00 UTC, shortly after the Spring Boot 3.4.0 release party.

Join me for mistakes, thoughtful pauses, head-scratching, a rant or two, and maybe some actual #Java coding of an #EventSourced game using #HTMX and #SpringBoot, all done with #TDD.

https://jitterted.stream

JitterTed - Twitch

Ted M. Young is a Coding Coach, Technical Trainer, Programming Presenter, and amateur guitar player. Focusing on Java, Spring, TDD, OOP, Hexagonal Architecture, and the Science of Learning.

Twitch

Today's stream starts earlier than usual at 20:00 UTC, cuz it's raining.

Join me for lots of mistakes, puzzled looks, rants, and maybe some actual #Java coding of an #EventSourced game using #HTMX and #SpringBoot, all done with #TDD. (is that enough hashtags?)

https://jitterted.stream

JitterTed - Twitch

Ted M. Young is a Coding Coach, Technical Trainer, Programming Presenter, and amateur guitar player. Focusing on Java, Spring, TDD, OOP, Hexagonal Architecture, and the Science of Learning.

Twitch

We've arrived! An example of #eventSourced user management in #fsharp using #marten awaits you in the newest post in my dev journal series: https://blog.mavnn.co.uk/2024/03/05/dev_journal_4_2.html

A website that users can sign up for and log in to. Exciting stuff.

Also, I am currently the world's only expert in the "julienned domain sandwich" architecture style, so you should probably hire me to help you implement it in your project.

Log in, log out: Dev Journal 4 (part 2)

Thanks to the @team for the hard work and the beta version of the new #eventsourced #neoscms 🥳🍾

in this post i write about and show how to merge #aggregates in #eventSourced systems (particularly with the #dolittle #sdk)

https://www.eke.li/2023/05/merging-aggregates/

#ddd #dev #code #systemDesign

Merging Aggregates – Ekeli

Generating domain-driven code – Ekeli

Where a single command gives rise to more than one event (in an #eventsourced system) you can design the order in which you emit those component events.
The (accidental?) conflation of #eventsourced and #eventdriven systems is going to be a major problem in the year ahead...

No surprise that implementing such a feature is really straight forward in an #eventsourced system. Everything feels natural.

Iterate through the event stream, count the number of finishes cards (tasks), memorize which achievements were already granted, check the specs and produce a new event if a new achievement (or level) was reached.

Should we want to introduce temporal achievements like „finished tasks per week“ - easy peasy, the time is in the events.

3/x

Turns out, I have not really declared my huge 💛 for #eventsourcing since I‘m on Mastodon. 😺

We‘re building a company-internal social card game @MaibornWolff with #golang - and it’s #eventsourced

If you want to learn about the #domainlogic of the game, I described it here:

https://medium.com/@TonyBologni/domain-driven-design-vs-functional-core-imperative-shell-4a38c6c86733

After many busy months I was finally able to work on the game again, mostly while spending ~10 hours in the 🚆

1/x

Domain-Driven Design vs. “Functional Core, Imperative Shell” | Medium

Sometimes different paradigms are forces that pull our code in different directions. I’ll try to describe such a situation with Domain-Driven Design and Functional Programming.

Medium