There are plenty of resources out there for learning language paradigms, discrete math, and CS theory, so that&#x27;s firmly on a junior dev&#x27;s shoulders to take up,practice, and eat, breathe, and sleep.<p>The rest, it seems, comes down to mentorship&#x2F;guidance&#x2F;learning on the job.<p>But it also seems that some of this guidance can very easily be learned by the junior dev himself&#x2F;herself (and thereby making mentorship more fun and less &quot;What the hell, dude&quot; for the senior engineer).<p>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?
What are concrete examples of mistakes junior devs often make?