definitely true. being a senior dev at this point, i look back and think about the devs who mentored me (which i didn't think of as mentoring at the time, like you pointed out i was trying to make my mark haha) and i'm like "i GET IT!" i see the same mistakes i made (over-engineering solutions, tightly coupling my use case to a proposed solution, trying to write code for a future case that likely will never appear or at least how i think it will, overdoing refactors, etc.) and i try to impart to young devs that they're like baby scorpions putting the stinger to everything in front of them when most things can be done simpler which will make their lives (and the lives of their teammates) so much easier down the road. i also try to help them with growing their career (i was also uncomfortable with these discussions, and thought i'd PROVE why i should get paid as much as my colleagues but the truth is, once you take a reduced rate it's locked in with 95% of employers) and understanding work/life balance more than i did in my 20s. sure, your current task might be "high priority" but there's one right after that, and right after that; you'll never get through all the high priority tasks and be able to relax, so learn how to prioritize yourself and your own health first because most employers are happy to let you work yourself to death for what is very likely an under-salaried workload.