Comment Re:There are always late adopters (Score 1) 23
Despite the headlong rush into AI, there is still a significant number of developers who don't believe in using AI, either because they don't think it works, or because they like coding by hand, or they just haven't learned to use it yet. There are event people who still write *COBOL*. Just because the tide has shifted, doesn't mean everyone is on the bandwagon.
From the POV of a non-programmer, I'm wondering if using AI effectively might be at least as much about having it answer questions as about writing the code. Note that those questions may include having one AI check another AI's homework.
Just recently I've been using AI a lot for the programming-adjacent project of putting LineageOS on a Pixel phone. I was using ChatGPT, and some of its advice didn't smell right so I decided to search for primary info beyond what was on the LineageOS site. I tried DDG, but its results sucked, possibly because I have the AI feature turned off. So I went to Google, where AI is pretty much unavoidable.
Google contradicted ChatGPT, and its answers seemed more in line with my past and present experience. It also assumed that I was asking for instructions. The ones it gave were clear and seemed quite sane. So I ditched ChatGPT and ended up using GoogleAI to guide me through the process of installing the OS and dialing in the system to my liking. It took some wrangling and a few trips down dead-end alleys, but overall I've been very happy with the results.
I can easily imagine that in other cases, ChatGPT's output would be better than Google's. So maybe using one AI to check another AI's output would also be worthwhile when doing real programming?