backtobasix
Joined 1 year ago
Joined 1 year ago
I know this is an unpopular opinion, but I'm here to burst the echo chamber bubble that "RTO is evil greed". There is literally merit to it, but if you haven't had broad perspective managing and delivering successful and unsuccessful projects, it will be invisible to you.
Some people just want to sit in a cube in code forever and ever. Awesome, that's great. But don't pretend you have insight into the larger processes above you if you don't take time to learn and experience them.
Fumbling with a mouse to write a word or draw a straight line is 10x slower than pen. Sorry, I think you're either used to working slow, or strait up bs'ing.
I've been in tech since 1990. My first job at IBM, my entire product team of ~100 people was on one floor of one building. We knocked out projects at an insane rate.
Today, trying to lead teams over zoom, across multiple time zones, means it takes weeks to solve problems that took a few hours over a whiteboard.
If I was a CEO I would mandate RTO, but I would also make sure to colocate my teams, otherwise there's very little point to RTO when you're just calling into a Teams meeting.
Of course, the downside no one is talking about: camaraderie is real. If you're an engineer with <5 years experience you probably don't see it, but a very large part of team success is how they work together, and in-person collab is priceless.