4 ms·
You tell the AI what broke and it fixes it, and this is usually a better experience than contacting support. But what if that fails? This might not generalize
by skybrian 2mo ago
You tell the AI what broke and it fixes it, and this is usually a better experience than contacting support. But what if that fails?
This might not generalize beyond developers, or at least not right away. Even if we’re not doing the upgrades ourselves, we know what a merge conflict is, and we’re probably better at telling the AI what went wrong so it can fix it.
These don’t seem like skills that are all that hard to learn for someone who’s interested. Also, merge conflicts an AI can’t deal automatically likely mean something major changed upstream.
There will be jobs helping people who get into more trouble than they can dig themselves out of. And if you can’t afford that, I guess it’s a learning experience.
- doc_ick 2mo agoGoing down that trail, eventually ai will eventually learn how to manage merge conflicts better (or whatever new scam). Or it could simply rewrite its own fork and support it all without user direction or supporting the core effort. All potentially with the ai model(s) running with no secondary prompt other then “make git error commands sarcastic”