Transcription
Quick random thought about using AI and how it once again relates to human leadership.
So see that highlighted blue line right there that says the original placeholder registry before my edit was actually right about the sheet. I changed the docs without checking the live schema. So what it's saying is it it made changes. Cloud code made changes to the way it was doing things without checking the actual hard fast rules, the schema of how this thing should be set up.
I almost got a little bit frustrated for about two seconds because and because now it's asking me, well, how do I want to fix it? And I'm like, well, go fix your own mistake. And like I said, I caught myself getting a little bit frustrated with this thing for, you know, just just deciding to make a change.
And what I realized is I did not tell it to go in the in that prompt. I did not tell it to pull up and read those files and verify the way things should be structured before writing that little piece of code. And typically I do that. Uh got a little lazy I guess and and rushing and just not thinking through um my commands.
And so what that reminded me of when it comes to human leadership, pretty sure this is a lesson from Joo Willink's Extreme Ownership 2, is that anytime something goes wrong, the first response should not be to blame the person whose task it was, which is me wanting to blame that for why didn't you why did you do it that way? The first response should be to question is the system broken? Is there something in the process or system that I gave to this individual, in this case the AI, that needs to be fixed so that this doesn't happen again.
So where am I shifting the blame from? I'm shifting it from this or the team member back to myself as the leader or the user. And it's me who needs to change what I do in order to get the results I want.
There you have it. Today's lesson in AI and leadership.