Great Dead Code episode with @ted.dev, on TDD and (what else!) Event Sourcing

Videos from the last @friendlyrb.com are finally up, and of course I’ll recommend @jan.dudulski.pl ‘s Event Sourcing talk. He does an excellent job at explaining the patterns from the ground up! m.youtube.com/watch?v=9oJz...

We were too late to the portable AC-buying frenzy

I want to be careful about confirmation bias, but this is an interesting read whatever your opinions on the matter zweiundeins.gmbh/en/blog/spa-...

Band playing a cumbia version of Radiohead’s Creep, and it’s kinda catchy

I don’t think it could be any clearer how urgent it is for European governments to decouple themselves from US tech.

This is kinda elegant. Here, even the Submit button is just another step that depends on the outputs of all the other steps, so it unlocks itself once all other steps have run. I also added indicators to show how you can partially complete inputs for different steps until requirements are met.

Playing with dataflow programming. Steps in a workflow are run asynchronously as soon as their inputs become available, in whatever order (or concurrently). Linear/concurrent execution is driven by dependencies, not pre-defined order.

@drbragg.dev hi! I listened to your Datastar episode with Delaney. I wrote the Ruby SDK and have opinions on the patterns and architecture it enables (asynchronous CQRS etc). Happy to answer any questions if you try it!

"You already event-source everything you trust" www.linkedin.com/feed/update/...

Because I've (stupidly) decided to write my own web framework, I now need to re-invent a lot of wheels, such as configuration APIs, class loading, etc. There's plenty of open-source libs I could use, but it's an opportunity to think from first principles. Fun work. And also pointless.

I love bookshops, but I also love my Kindle. Is there not a thing where you can peruse books in a bookshop, and then buy the digital version off them, right there?

I’m a total arachnophobe, but these little guys/gals are so cute

between this post and an episode I just recorded of Dead Code, really feeling like playing around with building an event-sourcing system https://ismaelcelis.com/posts/2026-05-wip/

New blog post: My Work in Progress Ruby stack ismaelcelis.com/posts/2026-0... #eventsourcing #cqrs

Sometimes I’m surprised at just how many unrequested opinions I seem to have in me

8yo makes these super complex origami. It takes >40m to make one and >100 folds in some cases. He seems to not only memorise the steps, but somehow understand them spatially. This is a picture of me trying to follow along. It's like encountering an alien super-intelligence.

Do I get a tax rebate from wasting all morning on the phone with HMRC fixing their mistake that they'd said they'd fixed already?

Background jobs are the wrong abstraction. It's one of the many patterns in CRUD-land where we spend ages debating syntax and style, but unquestionably accept the broader pattern as a fact of life, holding architectural thinking back.

Trying to find a term or acronym that encapsulates the set of patterns I'm using to write reactive, server-rendered, command-driven apps. SHARP: Server Hypermedia, Asynchronous Reactive Push CHARM: Commands, Hypermedia, Async, Reactive, Multiplayer CRISP: Command-Routed Immediate-mode Server Push

Men shouting unintelligible things on the streets, loud car horns everywhere. I’m going to assume it’s a football thing.

The fact that some animals’ expressions are so easy to read by us seems very profound somehow. Starting by our species having evolved intelligible expressions in the first place.

Lots of interesting looking Ruby jobs, all of a sudden

Long conversation about the complications of soft deletes in one of the Discords. Me trying to not bring up Event Sourcing again.

If you build an audit trail for your app, but the audit trail is separate from the data being audited, then you don't really have an audit trail. I was bit by this today, for the nth time.

Vibe-coding a chess app with my Ruby Event Sourcing and reactive web app libraries. All interaction is server-rendered, which makes things like highlighting legal moves simple. And time-traveling, of course, because always show off if it's easy!

I may have gotten a bit carried away with this work github.com/ismasan/side...

Great in-depth article on how PHP's Ecotone framework scales event-sourced projections. This is very similar to the design I arrived at. IMO partitioned event reactors are non-negotiable. blog.ecotone.tech/when-one-wor...

Sidereal's scheduled triggers (WiP) are 🔥. You define when commands are dispatched, on a fixed or recurring schedule. The example is a bounded schedule that starts 20 seconds after boot, recurs every 3 seconds, and ends 10 seconds later.

I've been working on three different Ruby libraries that solve (in my mind) different problems, but together make for my dream toolkit. Sourced - event sourcing and workflows Steppe - self-documenting HTTP APIs (and MCPs) Sidereal - command driven, reactive apps I have a clear integration plan now

Huge news for our corner of the Ruby world, and the culmination of a multi-year effort to align our people, our code, and our presence on the web. Go check out the new site, it’s stunning! Deepest of thanks to @aaronmoodie.com and @makenosound.bsky.social for co-creating these wonderful visuals. 🙇

Sidereal's built-in filesystem store now supports scheduled commands, and retries with exponential back-off built on top of them. All done via Ruby fibers and atomic file renames.

This simplifies most of the things I've been patching together for the last year honker.dev

Sidereal's built-in filesystem store now supports scheduling commands to run later. Here, starting a donation sets a command to run X seconds later.

Working on filesystem-backed Store and Pubsub implementations, so that out of the box Sidereal works across multiple processes. Goes well with SQLite for your own data. Later I might add optional networked implementations (Redis, NATS, etc)

A command-based web framework means you can send commands to the running app from anywhere, and the UI will just update accordingly. Down with the tyranny of the request/response cycle!

Listen to this man!

I had a great time at Haggis Ruby in Glasgow. My (first) Event Sourcing and Ruby workshop packed a little more material than the time permitted, but I hope it was useful to people! Big thanks to James and the organising team.

Two weeks of (intense) family holidays followed by two conference talks in a row. This will be an April to remember.

Last week’s talk at @wrocloverb.com is already up (that was fast!). Building reactive systems with Ruby and Event Sourcing. Big thanks to the team! youtu.be/Q6owchf4WEo

The landscape on the way to Scotland is just so ridiculously postcard-pretty. I want to get off the train at every random little village and just walk around for a day.

Off to Haggis Ruby in Glasgow!

This is a great summary of the zeitgeist I've been exploring in Ruby for the last few years. It feels like it's just the beginning! dev.to/siy/the-quie...

This is the model for a demo app I used for my Event Sourcing talk at @wrocloverb.com . Simple, explicit step-by-step flow threading together all parties to a workflow, from backend to UI screens.

You can rebuild state from events. But you can't rebuild events from state. Think about football. If you see 2-1 on a scoreboard, you know the current score, but not how it got there. That's the problem Event Sourcing solves: www.youtube.com/watch?v=xPmQ...

Just use a queue justuseaqueue.com

Compilable event models. What an ambitious project! www.weltenwanderer.dev

This will always be present day science fiction to me

I’m never late to airports anymore. Is this what being an adult feels like?