As someone who was (fairly recently) once there, this is definitely true. I think I'm pretty smart but if I knew then what I know now about potential resources and methods, I would have done much better and wasted much less time and energy.

There's the matter of the veteran having more problems to solve than the novice, so they tend to dismiss different things as "unimportant", for better or for worse.

In front of the exact same code, the veteran will bring forward issues such as deliverability on schedule, integration, letting the end-user start the program at 4pm and still be on time to grab the kids at school, the amount of paperwork and convincing that needs to be done so that the people at marketing can understand the new tech well enough to actually sell it to a customer or so that the people at IT can properly install and maintain it on a production environment without calling him every other night.

The novice will say: "why is there a break in the pattern here?", "this code fails when x is negative", "this monster piece of java code looks like what I saw someone solve with a one-liner in python last week".

Putting them both in front of a screen from time to time might either get you the best of both worlds, or hours of painful & pointless arguments.