Post #2189078
2026-04-02 23:30 UTC
@ambv@mastodon.social @jacob@social.jacobian.org Definitely...
I was going to say something about accountability, but this is pretty much my thought too.
Especially as it's incredibly unlikely that anyone would one-shot a perfect implementation, even more so for something that is extremely critical.
If we can't understand "why" something went wrong, how do we account for it? Was it negligence? Can someone be held accountable? Is the prompting wrong or is the code wrong?
I can see why that's a dream scenario for a corporation, though.
Replies (1)
-
@jacob@social.jacobian.org 2026-04-03 00:20
@pythonbynight@hachyderm.io @ambv@mastodon.social Ok yes I like this: “explainabibility” (I need a better word but fine) is one reason why code quality matters. Like, if a dam fails, we’d really like to have the blueprints — and for them to be readable! — so we can figure out where we screwed up. “The dam works because the lake holds water” isn’t sufficient.