They did! Also crafts, buried their dead, etc. AFAIK there’s not much evidence they were psychologically different from us in any meaningful way.
I need to go back to Eventlanes. I have a laundry list of improvements but I’ve been distracted with backend stuff (event sourcing, of course!)
I don’t think it could be any clearer how urgent it is for European governments to decouple themselves from US tech.
Each step defines expected inputs and outputs, so the workflow can also be checked statically for correctness.
Band playing a cumbia version of Radiohead’s Creep, and it’s kinda catchy
For references these are some of the things I'm using it for, but the general patterns are portable to any framework (or no framework) ismaelcelis.com/posts/2026-0...
This looks really good!
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.
@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!
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.