This has its detractors - sure, unless you've worked this way, you might find it intrusive that any dev can shoulder-surf at any time - but after a few days it rapidly becomes clear that such a configuration encourages developer participation, and more particularly: honesty about what is going on.
Too many times, dev teams I've managed have been tripped up by the one guy who doesn't like to share anything and rather prefers to work privately without any oversight - well, those guys don't last long in an environment where everyones work is equally open for shoulder-surfing. And I have found, anecdotally, that the most productive devs really don't care if you shoulder-surf - and in fact those that openly invite it, are a net positive effect on the teams own morale. People really learn a lot faster, and are seemingly more motivated to share their work, when the cubicles are set up for observation and not privacy.
Just an anecdote, but I've seen this, effectively, in action over 3 decades now and its just something I insist is a great way to build a developer team. Those that resist it, usually don't have good reasons to do so, either ..