> Constant talk and interruption are not conducive to the work of a software engineer.
During the times you are coding, yes. But a software engineer is more than a coder, so there are times when collaboration is very useful.
During the times you are coding, yes. But a software engineer is more than a coder, so there are times when collaboration is very useful.
But nothing distinguishes a junior and a senior more than the ability to work independently.
More seriously though, it's part of skilled project management to organize work in such a way that seniors don't need to constantly collaborate to stay in sync.
(Although obviously those statements aren't absolutes, hence the use of the word "often".)
We are talking Months and Months" by stopping other teams going of at a tangent or flat out just not doing what they are told.
The seniors used to be called "architects," and the "driving projects/design" used to be called RUP.
Your seniors should definitely be thought leaders, but when they get "too senior" or "too important" to write code, the company is done innovating. That's a major organizational smell.
And if your code isn't expressive enough that the design can be extracted without major effort, then the two will inevitably diverge at some point. Many bugs will appear.