home.social

#eventsourced — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #eventsourced, aggregated by home.social.

  1. Just to show you where my head is at, I had a half-dream of creating an #EventSourced travel calendar, like the one I have as a spreadsheet, in order to see the entire year at once. Each event would be the booking of a train, plane, hotel, conference, meetup, user group, etc.

  2. Just to show you where my head is at, I had a half-dream of creating an #EventSourced travel calendar, like the one I have as a spreadsheet, in order to see the entire year at once. Each event would be the booking of a train, plane, hotel, conference, meetup, user group, etc.

  3. Just to show you where my head is at, I had a half-dream of creating an #EventSourced travel calendar, like the one I have as a spreadsheet, in order to see the entire year at once. Each event would be the booking of a train, plane, hotel, conference, meetup, user group, etc.

  4. Just to show you where my head is at, I had a half-dream of creating an #EventSourced travel calendar, like the one I have as a spreadsheet, in order to see the entire year at once. Each event would be the booking of a train, plane, hotel, conference, meetup, user group, etc.

  5. Just to show you where my head is at, I had a half-dream of creating an #EventSourced travel calendar, like the one I have as a spreadsheet, in order to see the entire year at once. Each event would be the booking of a train, plane, hotel, conference, meetup, user group, etc.

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

    jitterted.stream

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

    jitterted.stream

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

    jitterted.stream

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

    jitterted.stream

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

    jitterted.stream

  11. 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?)

    jitterted.stream

  12. 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?)

    jitterted.stream

  13. 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?)

    jitterted.stream

  14. 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?)

    jitterted.stream

  15. 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?)

    jitterted.stream

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

    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.

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

    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.

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

    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.

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

    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.

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

    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.

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

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

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

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

  25. 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:

    medium.com/@TonyBologni/domain

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

    1/x

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

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

  28. 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:

    medium.com/@TonyBologni/domain

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

    1/x

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

  30. 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:

    medium.com/@TonyBologni/domain

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

    1/x

  31. 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:

    medium.com/@TonyBologni/domain

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

    1/x

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

  33. 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:

    medium.com/@TonyBologni/domain

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

    1/x

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

  35. Wrote an article on how to improve your Spreadsheets with Event Sourced architecture.

    With demo spreadsheet and background on #eventsourced architecture.

    "Event Source your Spreadsheets for Flexibility and Maintainability"

    berk.es/2022/08/16/event-sourc

  36. Wrote an article on how to improve your Spreadsheets with Event Sourced architecture.

    With demo spreadsheet and background on #eventsourced architecture.

    "Event Source your Spreadsheets for Flexibility and Maintainability"

    berk.es/2022/08/16/event-sourc

  37. Once I learned #eventsourced architecture, I realized that several systems which I wrote in the past, suffered because they weren't event sourced.

    It's one of those "if only I knew back then" architectures.

  38. Once I learned #eventsourced architecture, I realized that several systems which I wrote in the past, suffered because they weren't event sourced.

    It's one of those "if only I knew back then" architectures.