Your comment here is a bit terse, but I'm going to read it as promoting having options and agree with you based on that.
I think that it is quite possible that Agile doesn't serve the best interests of introverted programmers, but I disagree that this is a bad thing for programming as a whole.
There are plenty of introverted programmers. If the dominant office/workflow structure of the day makes them less productive than they would be on their own, that creates a huge opportunity for an office/workflow structure that makes introverted programmers more productive than they would be on their own.
On the other hand, I think that some percentage of introverted programmers who don't take a shine to Agile could search forever for an office/workflow structure that they like and never find one, because their issue is mainly with collaboration and exposing their work to criticism while it is still in mid-process.
This group of malcontents can be subdivided still further into those who can make it on their own and those who really would benefit from the sort of collaboration and criticism that they resist. It is this last group that aren't merely introverted, they are also faint of heart. I spend about 40-50% of my time in this category and it's real bad. I take solace in my relative youth and inexperience, I need to know that I won't be this sort of introvert for long.
My point was that there is not one perfect solution that fits for everything, this approach is negative as a whole. This video is just from another industry where they tried it in another area. It shows the corporate mentality in tackling problems.
The reality is much more complex especially when it comes to people with different needs. This makes it probably more difficult for companies, but when they produce software they have to invest in finding the best "solutions".
I think that it is quite possible that Agile doesn't serve the best interests of introverted programmers, but I disagree that this is a bad thing for programming as a whole.
There are plenty of introverted programmers. If the dominant office/workflow structure of the day makes them less productive than they would be on their own, that creates a huge opportunity for an office/workflow structure that makes introverted programmers more productive than they would be on their own.
On the other hand, I think that some percentage of introverted programmers who don't take a shine to Agile could search forever for an office/workflow structure that they like and never find one, because their issue is mainly with collaboration and exposing their work to criticism while it is still in mid-process.
This group of malcontents can be subdivided still further into those who can make it on their own and those who really would benefit from the sort of collaboration and criticism that they resist. It is this last group that aren't merely introverted, they are also faint of heart. I spend about 40-50% of my time in this category and it's real bad. I take solace in my relative youth and inexperience, I need to know that I won't be this sort of introvert for long.