Comment by patcon

I agree with your comment. but in defense of the articles scope: as someone trying to build longterm utility and developer infrastructure, I find the vibecoded prototypes to help me dial in on interfaces. Instead of waiting to hear back from only downstream user experiences (because you previously didn't have time to experience the various consequences of your choices yourself), you can get the various experiences under your own belt, and better tune the interfaces :)

Which is to say, the interface exploration comes part-and-parcel with the agent tooling in my experience

This comment is a little orthogonal to the content of the article, but my experience made what they wrote click with me