4 ms·

Except I also work with my local divisions, and the teams that work on the same floor near the same cubes are vastly more productive. I know this is an unpopul

Except I also work with my local divisions, and the teams that work on the same floor near the same cubes are vastly more productive. 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.

A4ET8a8uTh0_v2 2y ago
There is merit to WFO, but there is also merit to WFH. The problem is it is not being honestly discussed in terms of its merits. And we know this, because when WFH crowd actually notes verifiable metrics, management trots out unverifiable, unquantifiable serendipitous conversations at the watercooler. << 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. It is not my job to make my manager's job easier. It is management's job to make our job easier; not harder. The priorities are backwards, because management also happens to hold a lot of power over rank and file. Quite frankly, the management is simply too lazy to manage WFH well. << But don't pretend you have insight into the larger processes above you if you don't take time to learn and experience them. I only have anecdotes, but I am not sure you are right. Can you elaborate on the examples in your head?
scarface_74 2y ago
For the last 4.5 years, my job has been half supporting sales as the tech person working with them and the client and half leading a team once the sale closes. The teams and the customer are located all across the US. So I am definitely not one of the people who just wants to “code forever”. I’ll hop on a plane for a business trip in a heartbeat and have no problem with schmoozing, business dinners, etc I also have had experience delivering successful and unsuccessful projects. If I did a retrospective of each, none had anything to do with whether the team was collocated. While I’ve only done consulting remotely, I have been a team lead at a product company in office prior to 2020. I started working remotely and in consulting at the height of Covid in June 2020. It’s just that too many people haven’t learned how to evolve and work in a remote first culture. Before the gate keeping starts, I’m 50 and have been in the industry almost 30 years and I started in consulting when a job in the cloud consulting department at AWS (full time direct hire) fell into my lap and now I’m a “staff software architect” at a third party consulting company.
rubicon33 2y ago
For the record I totally agree. There are absolutely merits to in office work.

A4ET8a8uTh0_v2 2y ago

There is merit to WFO, but there is also merit to WFH. The problem is it is not being honestly discussed in terms of its merits. And we know this, because when WFH crowd actually notes verifiable metrics, management trots out unverifiable, unquantifiable serendipitous conversations at the watercooler. << 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. It is not my job to make my manager's job easier. It is management's job to make our job easier; not harder. The priorities are backwards, because management also happens to hold a lot of power over rank and file. Quite frankly, the management is simply too lazy to manage WFH well. << But don't pretend you have insight into the larger processes above you if you don't take time to learn and experience them. I only have anecdotes, but I am not sure you are right. Can you elaborate on the examples in your head?

scarface_74 2y ago

For the last 4.5 years, my job has been half supporting sales as the tech person working with them and the client and half leading a team once the sale closes. The teams and the customer are located all across the US. So I am definitely not one of the people who just wants to “code forever”. I’ll hop on a plane for a business trip in a heartbeat and have no problem with schmoozing, business dinners, etc I also have had experience delivering successful and unsuccessful projects. If I did a retrospective of each, none had anything to do with whether the team was collocated. While I’ve only done consulting remotely, I have been a team lead at a product company in office prior to 2020. I started working remotely and in consulting at the height of Covid in June 2020. It’s just that too many people haven’t learned how to evolve and work in a remote first culture. Before the gate keeping starts, I’m 50 and have been in the industry almost 30 years and I started in consulting when a job in the cloud consulting department at AWS (full time direct hire) fell into my lap and now I’m a “staff software architect” at a third party consulting company.

rubicon33 2y ago

For the record I totally agree. There are absolutely merits to in office work.