Such a joy to watch, especially after what they put is through last year.

Everything we do is immediately consistent.

We are event sourcing all the data, but in hindsight we should have only gone this route with some of the data. The history aspect is nice, but end users only care about the current state.

It appears there used to be a way to override themes in a config file per project, but I have not been able to make it work.

This makes having multiple worktrees open at the same time a bit more challenging, but the other benefits make up for this.

We took a lot of inspiration from your writings (commands and deciders are core components).

We ultimately wrote our own event sourcing layer.

Sure. It is an application for managing medical coder schedules. Hard to explain in a toot, but the event sourcing is primarily applied to managing (recurring) schedule changes and overrides.

This looks great. I have been using Strict (looks very similar) for an Event Sourced app the year and it has been fantastic- github.com/kylekthompso...

Have you guys seen/checked that gem out as well? cc @fractaledmind.bsky.social

I had a teacher back in high school that owned a very old beat up truck that he adored. It had a note on it saying the doors were unlocked, please don’t break the windows if you want to steal the stereo.