Earlier quoted context omitted.
Experience depends on which FAANG it is. Amazon for example doesn't allow Claude Code or Codex so you are stuck with whatever internal tool they have Meta, despite competing with these, is open to let their devs use better off the shelf tools.
I work at aws and generally use Claude Opus 4.6 1M with Kiro (aws’s public competitor to Claude Code). My experience is positive. Kiro writes most of my code. My complaints: 1. Degraded quality over longer context window usage. I have to think about managing context and agents instead of focusing solely on the task. 2. It’s slow (when it’s “thinking”). Especially when it’s tasked with something simple (e.g., I could…
I was thinking about this recently. This kind of setup is a Holy Grail everyone is searching for. Make the damn tool produce the right output more of the time. And yet, despite testing the methods provided by the people who claim they get excellent results, I still come to the point where the it gets off rails. Nevertheless, since practically everybody works on resolving this particular issue, and huge amounts of money have been poured into getting it right, I hope in the next year or so we will finally have something we can reliably use.