Asking someone to be a programmer in a loud chaotic open office environment is not dissimilar to asking them to program while juggling two balls and sitting on a unicycle. Its just excess difficulty that doesn't need to be added on top of the jobs.
Asking someone to be a programmer in a loud chaotic open office environment is not dissimilar to asking them to program while juggling two balls and sitting on a unicycle. Its just excess difficulty that doesn't need to be added on top of the jobs.
Then after the fact we made up a bunch of bullshit as to why this is some brilliant idea. Then this idea spread as if it was some kind of technological advancement because it worked for small tech companies trying to not spend money on furniture and walls.
We just aren't very good at any of this at scale. The open "office" and battle against remote work are different flavors of the same type of stupidity.
We have long since given up on getting any work done on our in-office days, but see them as collaborative / bonding / light planning only.
It's gotten to the point that even if we fly to each others city for a week, we might only go to the office 2~3 days, or by Wednesday/Thursday we might by physically collocated but go to different rooms in silence with headphones to actually get work done.
As a dev these days are actually pretty stressful as they have the feeling of creating work faster than doing any of it. It makes me remember how unproductive my dev teams used to be with the constant in-office interruptions. At prior jobs, I used to do most of my actual dev work after hours, and on unilaterally declared WFH days