Honestly if you do know what you’re doing that’s still true. They’re really good at looking like good code which makes it not always obvious when it’s not, even to an experienced developer.
Or maybe more bluntly, they’re really good at volume, not necessarily quality.
They’re really good at looking like good code which makes it not always obvious when it’s not, even to an experienced developer.
There can be a lot of difference between an experienced developer and a good/responsible developer.
Know your limits. Professional engineering has been wrestling with these problems for a long time - unfortunately the practices of professional apprenticeship, sealed drawings etc. have only informally been partially migrated into the software development world.
Honestly if you do know what you’re doing that’s still true. They’re really good at looking like good code which makes it not always obvious when it’s not, even to an experienced developer.
Or maybe more bluntly, they’re really good at volume, not necessarily quality.
There can be a lot of difference between an experienced developer and a good/responsible developer.
Know your limits. Professional engineering has been wrestling with these problems for a long time - unfortunately the practices of professional apprenticeship, sealed drawings etc. have only informally been partially migrated into the software development world.