←back to thread

We put a coding agent in a while loop

(github.com)
425 points sfarshid | 1 comments | 24 Aug 25 16:18 UTC | HN request time: 0s | source
Show context
VincentEvans ◴[24 Aug 25 16:36 UTC] No.45005596[source]▶
There will be a a new kind of job for software engineers, sort of like a cross between working with legacy code and toxic site cleanup.

Like back in the day being brought in to “just fix” a amalgam of FoxPro-, Excel-, and Access-based ERP that “mostly works” and only “occasionally corrupts all our data” that ambitious sales people put together over last 5 years.

But worse - because “ambitious sales people” will no longer be constrained by sandboxes of Excel or Access - they will ship multi-cloud edge-deployed kubernetes micro-services wired with Kafka, and it will be harder to find someone to talk to understand what they were trying to do at the time.

replies(16): >>45005632 #>>45005830 #>>45009697 #>>45009999 #>>45010075 #>>45010738 #>>45010794 #>>45011192 #>>45011626 #>>45011943 #>>45012386 #>>45013129 #>>45014577 #>>45014613 #>>45014836 #>>45015644 #
dhorthy ◴[24 Aug 25 17:04 UTC] No.45005830[source]▶
When Claude starts deploying Kafka clusters I’m outro
replies(3): >>45006053 #>>45010652 #>>45012753 #
Syntaf ◴[25 Aug 25 11:38 UTC] No.45012753[source]▶
I allowed Claude to debug an ingress rule issue on my cluster last week for a membership platform I run.

Not really the same since Claude didn’t deploy anything — but I WAS surprised at how well it tracked down the ingress issue to a cron job accidentally labeled as a web pod (and attempting to service http requests).

It actually prompted me to patch the cron itself but I don’t think I’m that bullish yet to let CC patch my cluster.

replies(1): >>45014483 #
1. dhorthy ◴[25 Aug 25 14:49 UTC] No.45014483[source]▶
oh yeah we had claude diagnose a production k8s redis outage last week (figured out that we needed to launch a new instance in a new AZ to pick up the previous redis' AZ-scoped EBS PVC after a cluster upgrade).