alt Hacker NewsI agree with your point in the broad sense, but the example might be bad. If sqlx is an important crate, and not stable yet, upgrading it without reading the changelog is honestly a flaw in your team process. Using the AI to fix organisational issues is typically one of the reasons I'm very skeptical of AI improving productivity in the long run.
I'm not taking a shot, to be clear, we had a similar issue a few years ago and we made sure this wouldn't happen again, that's absolutely not a shot, nor do I think it's a character flaw to use AI, au contraire, this is a very good use. I'm just worried that because AI is so good at fixing minor issues caused by governance/organisation flaws, we will be stuck using it to fix those and be trapped in mediocrity (that's not an issue for me, mediocrity is where I work best, but I'm a bit sad for the great Devs I've worked with.)
> If sqlx is an important crate, and not stable yet, upgrading it without reading the changelog is honestly a flaw in your team process
It’s not in the changelog though, this is an update of a transitive dependency that inadvertently changed the default behavior. sqlx didn’t document this because they didn’t even know it changed.
Even if it was a documented change, our process caught it because it was caught by CI. The issue itself was only a result of how our CI was configured (we had a database url with a domain socket path that didn’t explicitly specify a username, and we inadvertently relied on the default of “the current user”, which the whoami crate now defaults to “anonymous”.) I don’t see an issue in our “team process” (whatever that means) at all.