Most senior devs I know use it as a rubber duck. It's good at generating simple things that are 60% to 100% correct. It's good at summarizing high level conce

Most senior devs I know use it as a rubber duck. It's good at generating simple things that are 60% to 100% correct. It's good at summarizing high level concepts or summarizing how multiple high level concepts relate with 60% to 100% accuracy It's ok at helping you think about things to troubleshoot when you have an error you're not sure to do with. To be honest I would say it's actually not going to be good for junior devs because they don't have the skills to properly fact check, quickly. But for more senior folks it's very easy to immediately see what's wrong, ignore those parts or ask it for clarification, and use what's right. If you mostly know what you're doing, it can be very helpful to get immediate feedback, niche examples targeted exactly to what you're working on, or summaries of whatever high level concept you need a little more clarification on. Much much faster than spelunking through Google. As a concrete example I just this morning had it summarize Python's asyncio Queues versus Tasks, what they are, a few examples of using them, and when you would want to use one versus the other. All in just a few minutes.