| ▲ | JackSlateur 14 hours ago | ||||||||||||||||
Here is a sample We are talking about a "stupid" tool that parses a google sheet and makes calls to a third-party API So there is one google sheet per team, with one column per person One line per day And each day, someone is in charge of the duty The tool grabs the data from the sheet and configures pagerduty so that alerts go to the right person Very basic, no cleverness needed, really straightforward actually So we have 1 person that wrote the code, with AI. Then we have a second person that checked the code (with AI). Then the shit comes to my desk. To see this kind of cruft:
And then, we have 5 usage like this:
No HTTP keep-alive, no TCP reuse, the API key is passed down to every method, so is the API's endpoint. Timeout is defined in each method.
The file is ~800 lines of python code, contains 19 methods and only deals with pagerduty (not google sheet). It tooks 2 fulltime days.These people fail to produce anything meaningful, this is not really a surprise given their failure to do sane things with such a basic topic Does AI brings good idea: obviously no, but we knew this. Does AI improves the quality of the result (regardless of the quality of the idea): apparently no Does AI improves productivity: again, given this example: no Are these people better, more skilled or else: no Am I too demanding ? Am I asking too much ? | |||||||||||||||||
| ▲ | simonw 11 hours ago | parent | next [-] | ||||||||||||||||
Try pasting that full code into Claude and prompting: > No HTTP keep-alive, no TCP reuse, the API key is passed down to every method, so is the API's endpoint. Timeout is defined in each method. Fix all of those issues. | |||||||||||||||||
| |||||||||||||||||
| ▲ | ej88 11 hours ago | parent | prev [-] | ||||||||||||||||
I'm sorry your teammates have skill issues when it comes to using these tools. | |||||||||||||||||