I was disappointed when the coworker at my workplace asked AI about specific solution to minor dilemma. I thought about making minor change to the part of code that retrieves path to user's Downloads folder. Despite Windows Vista being almost 20 years old, .NET still doesn't have the normal means to retrieve path to that folder, Environment.SpecialFolder enum is still stuck in Windows XP era. Unless something changed in .NET 10? Not sure, the relevant issue is still open on GitHub.
AI generated pretty much the same solution how it was done in current code, so get user's profile directory through the usual means, then append hardcoded "Downloads" to path, so it would end being used / created, even if user moved Downloads somewhere else. AI also added the mysterious "using" referencing "Shell32" namespace. It didn't explain where the namespace came from.
That coworker got all mad when I mentioned using WIN32 API to get it, due to supposed plans for Linux builds. As if you'll do updates the Windows way. Well, who knows, but even so, few extra lines of code won't kill you if you'll have to overhaul that whole application anyway.
Another coworker also seems to love using AI, sometimes even remarks it in commit messages.
Programmers are weird. Perhaps staring at the code for thousands of hours fried their brain long time ago.
Sometimes AI can point you in the right direction, but generally, it's a mixed bag. TBH, I don't know the right approach for learning programming in general. There's so many specifics and conventions to do things. How do you know if a part of the task can be accomplished by your runtime library and where do you find the right method? Do you just start by studying some fat book / documentation?
The only book on programming I remember starting and finishing was The C Programming Language. I was still pretty clueless at the end.
I'm also not sure whether AI is making us dumber. Is it much worse than spending lots of time researching on your own and moving at snail pace?