We are a happy user of DBOS. I’ve been building out a lightweight TUI for managing our DBOS application internally, since we have workflows with tens of thousands of steps. I know the team is working on improving conductor for this use-case, but our internal TUI handles it pretty well for now. Hoping to open source it, but the code is a wreck atm. Anyways, I say all this to say, DBOS has a good client that can communicate with the instance easily, so building out a UI that fits your specific needs should be fairly simple.

oh man, don't even bother with bazel... hermetic python builds are such a mess.

Yeah, I burn my face on that particular stove once every 3 years or so.

For repeating objects of the same structure, yaml will still require each key on each object, whereas this is a hybrid with csv, so it defines the keys once.

No one forces us to use objects in JSON with repeated keys you know.

Indeed a

    {"header": ["some","column","names"], "values": [[1,2,3],[4,5,6],...]}

could fit.

For sure, but most people aren't thinking intentionally about what they are dumping into their context either ;)

Code is also unique in its suitability for agentic grep retrieval, especially when combined with a language server. Code enforces structure, semantics, and consistency in a way that is much easier to navigate than the complexities of natural language.

I recently got a Daisy Pod (https://daisy.audio/product/Daisy-Pod/). It supports a few different runtimes, including a max/msp runtime and a Pure Data wrapper called Plug Data. It's a pretty neat little device, even though the documentation could use some work.

I've been working on building something using a Daisy Seed lately. Pretty amazing that I can have interesting sounds (and effects) generated in just ~200 lines of C++.

And you're absolutely right about the documentation.

Doing quite a bit of that as well, but I’ve held off moving anything to gpt-5 yet. Guessing it’s a capacity issue right now.

This was my problem with Dagster, too. All the documentation and all the examples encourage you to split items into small discrete tasks. Then you realize that their cloud pricing is absolutely bonkers if you go over the paltry 30k credits… unless you sign up for a meaty annual enterprise contract. Got a $500 bill for something like 13k executions over the limit. That’s less than 45k executions in a month. Just for comparison, our main product’s sidekiq queue processes tens of millions of jobs every single day. Just a silly imbalance. I ended up having to combine a bunch of tasks to the point that I started asking myself why I was even bothering with using it at all.

I've had a Lamy Swift (palladium) for about 8 years now. It's a great pen with a unique clip mechanism. The Lamy rollerball refills are really nice, but they don't have a fine point version, so be ready for thick lines. I actually like the broad tip though. I just checked the Lamy website, and it looks like this pen has basically doubled in price since I bought it... yikes.

k2 on groq is really bad right now. I'm not sure what's causing the problem, but they've said that they are working on a few different issues.

best move is to switch to based-pyright