That's not controversial, but authority of "senior VS junior" often does not correspond to "expert VS non-expert". Seniors are often seniors because they just got stuck with the same company for a long time, or because, even worse, they wrote code that nobody except for them can maintain. That's why the development process should never be structured hierarchically, as it will kill fresh ideas and make bright developers suffer. There is, of course, a great learning opportunity if less experienced people choose to learn from more experienced, but don't forget, the best mentors are open-minded and are also willing to learn from fresh ideas. Learning should always be a 2-way process.
That's not controversial, but authority of "senior VS junior" often does not correspond to "expert VS non-expert". Seniors are often seniors because they just got stuck with the same company for a long time, or because, even worse, they wrote code that nobody except for them can maintain. That's why the development process should never be structured hierarchically, as it will kill fresh ideas and make bright developers suffer. There is, of course, a great learning opportunity if less experienced people choose to learn from more experienced, but don't forget, the best mentors are open-minded and are also willing to learn from fresh ideas. Learning should always be a 2-way process.
For me the senior/junior & expert/non-expert correspondence was clear, so thank you for pointing out that it may not be clear to other people.
With the rest I guess I can only agree