To me, something like this is actually what vibe coding thrives the best at; tight, looped, easily verifiable, test-driven dev work. In fact, this is probably the field it can do with little or no intervention, if you're willing to waste tokens.
replyIs it? How is it verified that this catches all the potential edge cases of interacting with AWS? Or is handling all the edge cases of AWS not in scope?
replyLike, what am I actually getting here? Is it just happy path operations being correct here?
For real edge cases, it will be like any other software. Users get to be the guinea pigs and report bugs as they find them.
replyHopefully AWS has had enough internal guinea pigs before they published this!
In the near future, every case will be a real edge case and every one will be a guinea pig.
replyThe border between AWS and AWS emulator becomes fuzzy. And the users of AWS will be agents as well. A completely offline emulator will save a lot of resources and could be a great training ground for more focused (offline) models.
Back in the day, we assumed that when a major company open sourced code, that code would have problems. We invented all these things like ‘issues’ to deal with this.
reply