Statistically speaking a senior (more experienced) engineer is more likely to consistently deliver time saving results, while a junior is more likely to occasionally do it, if ever.
Proving it’s not a one time thing is what pushes you in the salary and seniority ranking.
Senior engineers have less opportunity to write time consumingly careful code because they get paid so much. Much easier to throw new great hardware at it.
The corporate structures that reward people who prove especially good at building the product with more meetings and less time building the product are perhaps not optimal in their deployment of resources.
Maximising the fraction of the product built by people who don't know what they're doing would however explain the emergent properties of modern software.
Proving it’s not a one time thing is what pushes you in the salary and seniority ranking.