AI agents: Less capability, more reliability, please

(www.sergey.fyi)

419 points serjester | 1 comments | 31 Mar 25 14:45 UTC | HN request time: 0.001s | source

Show context

narmiouh ◴[31 Mar 25 16:22 UTC] No.43536781[source]▶

I feel like OP would have been better of not referencing the viral thread about a developer not using any version control and surprised when the AI made changes, I don't think anyone who doesn't understand version control should be using a tool like cursor, there are other SAAS apps that build and deploy apps using AI and for people with the skill demonstrated in the thread, that is what they should be using.

It's like saying rm -rf / should have more safeguards built in. It feels unfair to call out the AI based tools for this.

replies(4): >>43537400 #>>43537480 #>>43537532 #>>43546631 #

outime ◴[31 Mar 25 17:31 UTC] No.43537532[source]▶

>>43536781 #

Technically, they could be using version control, not have a copy on their local machine for some reason, and have an AI agent issue a `git push -f` wiping out all the previous work.

replies(1): >>43542348 #

1. mdaniel ◴[01 Apr 25 02:54 UTC] No.43542348[source]▶

>>43537532 #

I know this trope appears fairly often, but in reality unless it's someone's copy of $(git serve) running under their desk with no CI attached to it whatsoever, the commit history still exists and one can recover from a force push by just typing the equivalent of github.example.com/MyAwesomeOrg/MyRepo/commit/cafebabedeadbeef

I hypothesize that a $(git fetch --mirror) would pull down the "orphaned" revision, too, but don't currently have the mental energy to prove it

↑