That's exactly right. Any product is essentially made up of a gazillion small tasks, whether setting up a framework or writing a database query. If just some of

That's exactly right. Any product is essentially made up of a gazillion small tasks, whether setting up a framework or writing a database query. If just some of those small tasks can be made quicker / easier using these tools, then why not? What I find most useful in this space is twofold: 1. Specificity: so yeh, I can look at SO or wherever and see responses to a semi-specific query, say about querying a database. And yes, I could post a question and maybe after a few hours if I'm lucky get a response. But with ChatGPT I can throw in the actual table and column names and get a specific response back. Most often it needs honing, sure, but it's most often a great starting point. 2. Being able to back-query. So the fact that history is maintained means I can say "actually, add in a column called X and can you make sure that the query only returns unique IDs" and - again - I'll get an immediate response without having to go all the way back through the questioning journey again. As with any tool, the extreme responses on either end seem obviously flawed. On the one hand: no, it's not going to replace all developer jobs. On the other, to just completely ignore it, not try it, always assume that "the documentation" is better - this seems blinkered and foolish too. Somewhere in the middle is a sweet spot where human brains collide with these tools and we manage to tease out code that is more quickly researched and saves time but also well considered and treated with a degree of healthy scepticism before deployment.