[jackyli02]

This is explicitly framing hand-written code as the wrong workflow. That's a significant shift from even six months ago. My sense is this will become more common at companies building on top of APIs and integrations (Zapier's core domain), where the code is more glue than architecture. Whether it scales to systems-level work is a different question. The failure modes of agent-written code are still poorly understood, and "built mitigations" is doing a lot of heavy lifting in that job listing.

[mattmanser]

I work in an API heavy domain.

Ironically, you need it to be right and LLMs don't cut it.

[raw_anon_1111]

My API heavy domain is coding against the AWS SDK

https://docs.aws.amazon.com/boto3/latest/

I am just linking to the Python version because it’s all on one page. All of the other supported languages are the same - they are all autogenerated from the same definition file by AWS.

Also consider these same APIs are surfaced by the CLI, Terraform, CloudFormation and the AWS CDK.

I’ve been testing writing code and shell scripts against the AWS SDK since 3.5. It helped then, I can mostly one shot it now as long as the APIs were available when it was trained. Now I just have to tell it to “search for the latest documentation” if its a newer API

[mattmanser]

There's a ton of examples of AWS in GitHub isn't there. You couldn't have picked a better API for an AI to one shot from the literally millions of examples it has.

I mean mapping one crazy API with tons of quirks from one non-software company to another non-software company that's often behind a username/password or some other barrier.