Categories
Antiwork

Tired of parallelizing

The phrase “in parallel” has been thrown around more than ever since WFH got started. Every time my team is faced with more projects than we can handle, my boss chimes in with, “Why not just do these all in parallel?” or “Can't you just do it asynchronously.” He's convinced that this method will allow us to work on many things at the same time, thereby increasing productivity and shorten the projects. Every one of these projects inevitably goes longer than he expects. Worse, the expectation seems to be expanding into every aspect of our roles: on-call duties, bug fixes, meetings, and the list goes on. Apparently, everything should be done “async” and 'in parallel” nowadays. Constant context switching is just terrible for software development and I was wondering if anyone else had a similar experience?


The phrase “in parallel” has been thrown around more than ever since WFH got started. Every time my team is faced with more projects than we can handle, my boss chimes in with, “Why not just do these all in parallel?” or “Can't you just do it asynchronously.”

He's convinced that this method will allow us to work on many things at the same time, thereby increasing productivity and shorten the projects. Every one of these projects inevitably goes longer than he expects. Worse, the expectation seems to be expanding into every aspect of our roles: on-call duties, bug fixes, meetings, and the list goes on. Apparently, everything should be done “async” and 'in parallel” nowadays. Constant context switching is just terrible for software development and I was wondering if anyone else had a similar experience?

Leave a Reply

Your email address will not be published. Required fields are marked *