I've been watching Dagger with great interest, although have not moved production workloads to it (nor, admittedly, even committed an afternoon to setting up any workflows/graphs).
Passive comment readers should be aware that ^shykes here cofounded Docker (my gratitude), so it's really worth a look.
Can anyone comment on the ergonomics of Dagger after using it for a while?
I was just looking at the docs earlier this week to consider a migration but got confused by the AI sections...
Yes, the whole thing. The only thing in the entire repo I wrote was the CLAUDE.md, which was the only file at the beginning.
I just fire up `claude` and say "Have fun!".
The only other nudge I've given it is once encouraging it to not be afraid to be ambitious, and that if it wanted me to distribute anything I would (and would provide it with user feedback if it remembers to ask me about it).
Interval trees or ordered segment sets are the "correct" answer but sometimes you can accept constraints in your domain that radically simplify– for example, with equipment availability and time slots, you may have a fixed window and allow for slots to only fall on 5 minute marks. With those 2 constraints in place, a simple bitmask becomes a viable way to represent a schedule. Each bit represents 5 minutes, and 1=avail 0=unavail
Hey congrats on launching–
Wanted to drop a note from someone who has been burned: avoid .xyz domains like the plague. They can revoke your control of the domain at any time if you end up on a spamhaus (etc.) list. This happened to me even though I was only using my .xyz for a non-prod env shared with a customer. One day control of the domain was just taken by the .xyz org and I had no recourse other than generic ticket submission.