bavell

1000% this. I encounter this all the time (with Claude) and it drives me nuts!

I don't see anything wrong at all with how OP approached this with their spouse.

Awhile back I built a project which reads comfy's API and builds a typescript sdk from it. Much nicer to work with and still benefits from node caching and the comfy ecosystem. Perhaps I should clean it up and open source it, though I haven't looked around and there may already be other projects doing this out there.

Perhaps "friction"? Agreed that it's hard to pin down, and comfort / convenience doesn't quite capture it.

How long did it take these companies to even notice? Why wasn't exploiting bugs in the agent sandboxes anticipated?

Human failures all around, though it's easier to just blame the models.

Android Firefox here, top nav takes up 1/3rd of the viewport

It's a bit of a nothingburger IMO, but charitably you could think of it as a rest API + bundled agent instructions.

I use Arch exclusively and haven't had any of the issues you describe.

That said, I do occasionally deal with quirks due to the rolling distro nature of Arch. The benefits far outweigh the occasional upgrade pain IMO though.

What was/is it like working with Hooded Horse? How did you get that going? I'm a big fan of the games they publish :)

Good luck on your game & launch!

I find it difficult to always have one or more long-horizon tasks 'queued up' and ready to run... I find myself usually bottlenecked on design, review, or something similar that requires me being in the driver's seat. It's possible I could queue up a bunch of tasks, letting the LLM run off in multiple directions, but then I'd be less able to steer and course correct.

Just my experience though, I'm still figuring things out. Perhaps some subsets of tasks would be more ideal for these long-horizon workloads - exploration, multiple competing implementations, etc...

I find no comfort in it. Merely pointing out that 'some' is hand-wavy and perhaps technically true but meaningless to the discussion.

Precisely

Good read and matches my experience pretty well, but I'd humbly suggest the author look up the definition of 'vertical' and 'horizontal' and swap their terminology + fix their videos :)

'Some' is doing a lot of heavy lifting there...