Joel Spolsky's eighth item in the Joel Test asked a deceptively simple question: do programmers have quiet working conditions?
In 2000, that question was often about cubicles, doors, offices, and noise. In 2026, the question runs deeper. The modern threat to serious engineering work is not only a loud office or an open floor plan. It is the environment in which a developer is never truly allowed to disappear into the work at all.
Some organizations have recreated the worst features of the noisy office through remote work. They have taken a medium that could have supported autonomy, flexibility, asynchronous collaboration, and thoughtful silence, then used it to impose continuous shared presence instead. The language used to describe that arrangement is often upbeat and reassuring: collaboration, alignment, pairing, mobbing, teamwork, support. The lived experience can be something else entirely.
A more accurate phrase for some of these environments is continuous managed availability.
That phrase may sound severe, though I think it is precise. The problem is not collaboration itself. Pairing can be valuable. Mobbing can be valuable. Shared debugging can be valuable. Junior engineers and interns can learn a great deal by watching experienced people reason out loud. Hard migrations, incident response, tricky architectural changes, and unfamiliar codebases can absolutely benefit from intense synchronous work.
The trouble begins when a bounded technique becomes the default operating model for the whole day, every day.
Read More
