I’m trying to understand whether it’s mainly a replacement for specific WebRTC use cases, or more of a building block for new kinds of real-time systems.

A runbook can tell you what usually works, but it cannot tell you when the situation is no longer “usual.” That kind of judgment mostly comes from seeing real systems fail in messy ways over time.

Tools are still valuable, of course. But they work best when they help experienced people transfer knowledge, not when they are used as a reason to remove the people who understand the system.

I've run into similar problems when moving old content between systems, especially with MySQL and mixed encodings. It can get messy surprisingly quickly.

That said, single-attempt results are a bit hard to read into. For anything code-like, things like retries, test feedback, or just letting the model iterate tend to change the outcome quite a bit.

Even small mistakes can make something dealing with sensitive data hard to trust. It seems useful as a first pass, but I’d probably still want some deterministic checks or a human in the loop to feel confident using it.

Folding bikes always seem to push engineering into very unusual directions compared to regular bikes.

For anything touching security or privacy, even small inconsistencies can quickly erode trust.

Having better tools really makes a difference when revisiting old or half-finished projects.