They don't know what they don't know. (Devs not knowing where to start writing a piece of code that works on actual bytes and not strings or numbers is a classi

They don't know what they don't know. (Devs not knowing where to start writing a piece of code that works on actual bytes and not strings or numbers is a classic example of this problem.) Sometimes they are good devs in their space and mean well, but they spend their working lives on a different level of abstraction and in a different problem domain. The danger with co-pilots is that devs using them will even not know what to ask for, because they will not know what it is they need to write. There is value in going through docs, writing your own code, making mistakes, seeing your code fail, fixing it. That's how you learn to spot mistakes made by AI, but I don't think that having a coding puppy and spending time fixing its mistakes is conducive to writing better code or improving developer productivity.