What are concrete examples of mistakes junior devs often make?
There are plenty of resources out there for learning language paradigms, discrete math, and CS theory, so that's firmly on a junior dev's shoulders to take up,practice, and eat, breathe, and sleep.
The rest, it seems, comes down to mentorship/guidance/learning on the job.
But it also seems that some of this guidance can very easily be learned by the junior dev himself/herself (and thereby making mentorship more fun and less "What the hell, dude" for the senior engineer).
Is there a particular class of mistakes that junior devs almost undoubtedly make that they can make sure to be aware of before Day 1 on the job?
The rest, it seems, comes down to mentorship/guidance/learning on the job.
But it also seems that some of this guidance can very easily be learned by the junior dev himself/herself (and thereby making mentorship more fun and less "What the hell, dude" for the senior engineer).
Is there a particular class of mistakes that junior devs almost undoubtedly make that they can make sure to be aware of before Day 1 on the job?