Ha! See, my experience is a bit different. Most times, it acknowledges its error, and sometimes it successfully corrects it. That is, IF I give it specific eno

Ha! See, my experience is a bit different. Most times, it acknowledges its error, and sometimes it successfully corrects it. That is, IF I give it specific enough information (ex: "why do you treat this variable as a string, it's a number?", or "don't you need to unpack the json first?"). Other times, it fixes something, but breaks something else in the process, and no matter of coercing makes it go to where I want. But, yeah, the "confidently wrong" aspect needs to be kept in check. I tend to treat it as any other source of information... with a grain of salt. What's neat with code is that you can prove the "truthiness" of its affirmations pretty quickly.