
Remote Work Didn't Fix Toxic Culture—It Just Made It Async
TL;DR: Your team's dysfunction didn't disappear when everyone went remote. It just moved into Slack, and now it's worse because you can't read the room. I spent 3 years watching this play out. Pre-pandemic, your manager's bad mood was obvious—you'd catch it in a hallway conversation. Now? That same manager writes passive-aggressive comments in PRs at 11 PM and you're supposed to interpret tone through a screen. The real problem: We mistook silence for health. Remote work did expose one thing clearly—bad code, bad decisions, bad people all leave a digital paper trail. But instead of fixing the culture, teams just learned to code-switch better. The senior engineer who bullied juniors in meetings? Now they bully them in GitHub comments. The meeting-obsessed manager? Just scheduled 8 async updates instead. The Pattern Think of it like this: Old culture toxicity: visibility = high confrontation = forced resolution = sometimes happens Remote culture toxicity: visibility = hidden in timestamp
Continue reading on Dev.to
Opens in a new tab

![[MM’s] Boot Notes — The Day Zero Blueprint — Test Smarter on Day One](/_next/image?url=https%3A%2F%2Fcdn-images-1.medium.com%2Fmax%2F1368%2F1*AvVpFzkFJBm-xns4niPLAA.png&w=1200&q=75)

