Mate, I was buying a kebab and the guy was convincing me that the Earth is flat, there's no Moon. And it's proven by... something with shadows. At least I got a real kebab in the end.
The reason is a
lack of an immediate verification process. The reason LLMs are been great at programming but less so elsewhere is because if it generates non-working code, calling hallucinated libraries or functions, there's immediate feedback. That code doesn't compile, it crashes, it fails tests, it's slow, it's buggy. But if the LLM gives me bad relationship advice, there's no repl that it can use to retry that conversation with my now-ex until we're back together. Or whatever thing that it's being used for that doesn't have some sort of way to give it a verifier.
So taste is still a thing. Software engineering will have to develop (uh oh) taste and the ability to say no. Your app could include a button to make the device scream like a monkey, but if management tells you it has to have a feature that makes no sense, the answer is no.
Oh yeah, I love having to manage sync conflicts in my password database because I was dumb enough to edit it on two separate computers that weren't both online at the same time.
Yeah, my main reason to stay away from Keepass, everything is in a single versioned binary file. I like 'passwordstore.org', where every secret is it's own gpg-encrypted textfile in a git repo. Every change is a commit, easy to see history, easy to revert or know which version is newest. And easy to selfhost, you just need a place to git push/pull from.
reply