I think part of the reason for feeling like a know-all can-do-everything in junior years and afterwards as well is, because of not reading the right books. I am talking about really good books about the core competence of programming. I have read books authored by people with more than 50y of experience. The ideas and wisdom they come up with is unparalleled. Reading about such great ideas and how to avoid issues with code makes me feel like: "Woa that is sooo neat and clean! Why did I not get that idea myself?" and there you have the humbling experience, that should introduce respect for seniority.
Of course it is not a blanket. A senior should adapt to new ways as well, if they make sense. For example functional constructs have become more popular in recent years. Just because one is a senior, does not mean, that they should go on writing their sequential do-while loops (usually it would be for loops, but exaggerating here), when things could be written with multicore in mind and using map reduce style. That is not seniority, it is lack of self-education and development of ones skills. No need to join the web framework churn either though. One should understand their essence though.
Of course it is not a blanket. A senior should adapt to new ways as well, if they make sense. For example functional constructs have become more popular in recent years. Just because one is a senior, does not mean, that they should go on writing their sequential do-while loops (usually it would be for loops, but exaggerating here), when things could be written with multicore in mind and using map reduce style. That is not seniority, it is lack of self-education and development of ones skills. No need to join the web framework churn either though. One should understand their essence though.