←back to thread

504 points Terretta | 4 comments | | HN request time: 0.001s | source
Show context
RedMist ◴[] No.45064657[source]
I've been testing Grok for a few days, and it feels like a major step backward. It randomly deleted some of my code - something I haven't had happen in a long time.

While the top coding models have become much more trustworthy lately, Grok isn't there yet. It doesn't matter if it's fast and/or free; if you can't trust a tool with your code, you can't use it.

replies(5): >>45064677 #>>45065762 #>>45070615 #>>45072014 #>>45074876 #
1. Retr0id ◴[] No.45070615[source]
Why is deleting code a big problem? You have version control, right?
replies(2): >>45070724 #>>45071401 #
2. markerz ◴[] No.45070724[source]
Deleting extra code is easier than verifying deleted lines and restoring the ones that seem like an accident. It's just annoying.
replies(1): >>45071331 #
3. SamBam ◴[] No.45071331[source]
It's the X/DOGE philosophy -- cut things out, and when the smoke starts spewing, try to work out which of the many things you cut were necessary.
4. rs186 ◴[] No.45071401[source]
Because it's an obvious waste of time that should just never happen.

Not to mention that accidents happen, not everyone always has the good habit of using version control for every change in every project, and depending on the source control software and the environment you work in, it may not even be possible to preserve a pending change (not every project uses git).

I have heard real stories of software bugs causing uncommitted changes to be deleted, or causing an entire hobby project to be wiped from disk when it has not been pushed to remote repositories yet. They are good software engineers, but they are not super careful, and they trust other people's code too much.