1233. AI Lesson 2

 Since post 1232 AI Lesson 1 I have used Copilot many, many times. Most provided a solution that worked or got me close to working. However, it does have some annoying habits:

1. AI will always attack what it thinks your most recent problem is rather than the reason why you are there. For example, if you jump at its recommendations in first query and hit a snag doing it, AI focuses on that snag, Then if you try fixing that one to proceed and hit another snag (2), AI switches to that, etc. I have gone down a path of over 10-15 snags in a row throwing me way off the initial problem trying to solve each snag instead. Then you get to one that is a monstrous recommendation like download something to execute that you know is not involved with the initial problem. I was told about a .dll missing that never existed on my systems. AI couldn't be convinced that it was never part on my initial installation, granted many years ago in 2010. The application at fault was Any Password. It took AI about 40 minutes before telling me that fact and that it was discontinued and thus the module is gone. Fact though, is Any Password has worked for 15 years now without a hiccup and had its first one AI claimed was an encryption problem within. Not true. Works perfectly again whatever the problem was! AI believes it has to tell you details about why something isn't working. Half of the time it is wrong. This leads to incorrect analysis and recommendations re the major issue which is lost in the process.

Just beware of this annoying habit. Take what you can get from AI, CHALLENGE it if it is wrong. It always apologizes and throw out another THIS ONE WILL work. I had about 15 of those and all failed! Gather what you can and assemble the correct facts it or you find and proceed with those.

It can be a frustrating experience. One must understand that it is using data from man soles, right or wrong, to put its pieces together. I'm not particularly happy with it diagnosing technical computer problems as the "leader". I have found that you take what it offer and proceed with you know is right.

Always more than not the procedures to implement in the Android world are incorrect and something else must be substituted. AI does NOT confirm the starting point, i.e., device, device age, brand, software, etc. first. Instead it jumps into trying to resolve you issue with "hidden assumptions". So, my advice, just like a customer support person, begin with details about you hardware and software before he runs in the wrong direction. I'm still learning. But this AI is NOT a hands off tool that gives you correct answers. It must be told details. Life goes on.