I'm an "AI" skeptic, but yesterday I kind of had a win with Claude.ai. I needed to create a server that implemented a couple dozen APIs for a 3rd party service we're evaluating. The 3rd party service connects to these APIs to ingest data into its system. Since we're just evaluating this 3rd party service, I didn't really want to invest too much time writing APIs for it. I gave Claude.ai some clear instructions, and pointed it to docs for every API I needed. I also specified that wanted the API server set up as an AWS Lambda using the latest nodejs version.
The first attempt did not work, but I noticed that the "index.js" file was incorrect. It did not contain a "handler" function that the Lambda system requires, but that was in a separate file "routes.js" which was not referenced anywhere in the "index.js" file.
Deleting the index.js file and renaming routes.js file to index.js made it work. So, Claude.ai made a stupid mistake, but all the rest of the system worked. The couple dozen API files were correct, the example data was correct, and it actually worked once I pointed out the mistake to Claude.ai and it created a new .zip file of the project.
But I wasted a lot of my time trying to figure out why it wasn't working, and setting up API Gateway was another problem I had to figure out. It took me a few hours to get what Claude.ai wrote to work, which is about as much time as it would have taken me to just do it all myself.
Claude.ai is not really getting much better, but I'm getting better at expecting how Claude.ai is going to mess things up.
The downside of using Claude.ai is that I don't really know what it wrote unless I look through a few dozen files. I don't "own" that code, I don't feel invested in that code, but I could probably expand on it and eventually get familiar with it.