4 ms·
To generalize in a simplistic way: upper management wants to go back, everyone below doesn't. So publications targeted at the former will support office work wh
by cardosof 5y ago
To generalize in a simplistic way: upper management wants to go back, everyone below doesn't. So publications targeted at the former will support office work while others targeted at the latter will support WFH.
- foobiekr 5y agoAs a senior eng/architect I’d like to go back at least part time. My job, which mostly consists of keeping people from wasting effort doing things they shouldn’t and then getting upset when they’re asked to get back on track, is 100x harder remote because discovery of confusion and incorrect beliefs/approaches is delayed until the less experienced ICs have put in more effort. Engineers suck at sunk cost. This is far, far easier to do when you can overhear discussions, bump into people and ask, etc. even with a great deal of eyes-open effort over the last year to mitigate this, it is a problem. This only matters if you are doing complex technical coding. CRUD stuff, UI stuff, etc don’t have this problem as far as I can tell (UI people imho have the best attitude wrt change) but systems work where inter function efficiency matters is very much harder with 100% WFH.
- anotherhue 5y agoThis resonates so much it hurts. One element we have all DK'd ourselves into forgetting is whether we are good enough engineers to benefit from independent remote work? Of course we enjoy it, but from a business perspective, if we go down 3x more rabbit holes then it's not so attractive.