I've found the opposite to be true, actually. I'd prefer it in the hands of someone more experienced. Real world example: Hey chatgpt, write me some Camel rout

I've found the opposite to be true, actually. I'd prefer it in the hands of someone more experienced. Real world example: Hey chatgpt, write me some Camel routes to take an input off of a JMS queue, wire it up to the camel salesforce getSObject endpoint, use these headers for the lookup, and write some unit tests. Actual result: Code that is 99% correct, but messed up a couple of parameters and used a slightly wrong approach to mocking some things in the unit test. Having used all of the frameworks extensively, it took ~5 minutes to fix and certainly saved time. Partially because I'm used to reviewing code from people who make similar mistakes. I can't imagine that working out as well if it was a truly junior engineer (not just a junior in name only) who didn't understand what was going on with the code very well. And this is just the beginning. It is hard to imagine not using this for the bulk of the work within a few years.