The LORD was in the right, for I rebelled against his command. Listen, all you nations, and look on my agony: my maidens and my young men are gone into captivity.
The Revised English Bible (Cambridge; New York; Melbourne; Madrid; Cape Town; Singapore; São Paulo; Delhi; Dubai; Tokyo: Cambridge University Press, 1996), La 1:18.
If you want to fix anything, the first step is acknowledging that something is wrong.
I just got done revising a utility I created, or rather had Gemini AI code, for sharing site feeds between the various websites that are related to my publishing company, Energion Publications. An interesting thing about AI is that while it is not precise about doing what I want, as I’ve been accustomed to for decades, it can create a lot of code very quickly. This introduces a weakness. If I ask for the wrong thing, I generally get the wrong thing. The AI follows my plan for better or worse.
The configuration file for my utility was grotesquely complex. It was precisely what I had asked for. The AI produced code that did what I asked. But my plan was not very good.
After struggling for awhile to learn how to use the code I asked for I realized that this wasn’t going to work. I could probably figure it out, but I’d forget it in a day and then I’d have to start over. I played around with it for a few minutes, and realized there was a massively simpler way to set this up. Minutes later I had new code which works just fine.
The first step in fixing this was to recognize that there was something wrong.
AI’s, in my experience, are not good at recognizing what’s wrong. They usually dig deeper to make the current plan work. On this point, AIs are not that different from humans. Once we have chosen a path we’re likely to stick to it, whether it’s working or not.
This verse is a key. “The Lord was in the right.” Conversely, I was wrong.
Admitting error is often the gateway to success.