It could be that his situation is unique to him, and doesn't generalize at all. But it also seems plausible that the trend toward practices like sprints, stories, and open plan offices that aren't conducive to the kind of deep work that people like Bisqwit do.
It's also entirely possible that the churn and burn approach to development is what is most profitable in most situations, and that deep workers might find themselves relegated to certain niches.
None of that is meant as a knock on agile development, or any other development practices, of course. But I think it's worth stopping to think about what we give up when we dive headlong into the Agile, open office type of workflow. It would be interesting of more teams had the courage to try practices that are definitely not waterfall, but also not Scrum (which is what most shops that call themselves Agile are practicing). Something that values relatively short iterations, but also values the kinds of creativity and deep work that can't easily be broken up into sprints and stories.
