Comment by jwpapi
1 month ago
I don’t want every verb implemented, I also dont want an IETF standard. I want as little as possible, so I have to worry about as little as possible in the future.
Use-cases differ, you described a complete REST API, which can be as much of a problem as a too little.
I see you haven't encountered an API where a GET command can modify the database.
Similarly, I once worked somewhere that had an HTTP API that returned status code 200 {“error”: “ok”} to indicate an error occurred.
A lot of GraphQL APIs are like this! They return a 200 just to mean the damn GraphQL is well formed, and the call can totally fail underneath.
Now why would you make such a monstrosity? Audit logs? I was having good day till now.
I saw a code base where SQL UDFs were used to mutate the data with SELECTs...
Say what now
I have not either. What's your point? AI isn't perfect.
Then just tell it to do that
It'll even suggest it
You want a single RPC websocket go for it
Till it has explored the codebase, asked me follow up questions, suggested the code change, incorporating my fixes after losing time on context switch + the extra time I need when somebody requests a change in 3 months to learn the mental model. I’m way faster to just write it myself (mental model included)
If it's genuinely the case that you can write code faster than you can prompt it into existence then you're not being ambitious enough with your coding agent. Ask it to do more. Tackle bigger problems.
5 replies →