This reads as someone who has not learned how, when and why to use a new tool, uses it poorly if at all, and then blames the tool. All the while their peers wh

This reads as someone who has not learned how, when and why to use a new tool, uses it poorly if at all, and then blames the tool. All the while their peers who have taken the time to understand the new tool and when/how/why to use it are in fact using it very successfully. Instead of thinking "it doesn't work," think "when and how can this work for me?" I had an experience recently where I was working on a python notebook that I didn't create, and which was a bit old. I ran into an error that I was unfamiliar with. There had been added an AI-based "explain this error" button to my notebook interface. I figured it would suck, but I gave it a try anyway. It correctly identified the problem (old library conflicting with newer one), suggested the change (switch from old library to newer fork) and offered to implement it. I clicked "yes" and it made all of the (relatively minor) changes required, including a few spots where some method returns had changed and needed to be unpacked. I scrutinized the changes to ensure I knew what was going on, but it all just worked regardless. Probably 8 or so 1-2 line changes throughout 200 lines of code. This likely saved me roughly an hour, or maybe two, of fiddling around, googling, reading docs, etc. Because I had an open mind and gave it a try, and had reasonable expectations, which were in fact exceeded. I did not start with "refactor my codebase please," and then get mad and give up when it doesn't help much.