I've been told on one contract that my style was off-putting and making others on the team feel like nothing was ever good enough... at the _same time_ as a team on a second, parallel contract couldn't get enough of my time and thanked me profusely for helping them out of the hole they dug and teaching them to get better.
It's all about attitude and egos. There are devs who call themselves senior who are theoretically proficient coders, but who lack the "street smarts" of how to develop a useful product, and how to architect it well.
The person with 10y+ more experience is going to run circles around them. Not because they can crank out code faster, or with fewer bugs, but simply because they can do a lot more with a lot less, and they can contextualize what they code in terms of what the business is going to need 3-6-12 months down the line.
As a junior you can either be resentful and try to compete from afar (job A), or you can realize you had access to a wealth of knowledge and experience that can give you a multi-year headstart on your peers (job B). Choose wisely.
It's all about attitude and egos. There are devs who call themselves senior who are theoretically proficient coders, but who lack the "street smarts" of how to develop a useful product, and how to architect it well.
The person with 10y+ more experience is going to run circles around them. Not because they can crank out code faster, or with fewer bugs, but simply because they can do a lot more with a lot less, and they can contextualize what they code in terms of what the business is going to need 3-6-12 months down the line.
As a junior you can either be resentful and try to compete from afar (job A), or you can realize you had access to a wealth of knowledge and experience that can give you a multi-year headstart on your peers (job B). Choose wisely.