Premise: software engineers drastically underestimate how difficult it is to make remote work work well for a company. Writing code remotely is the easy part. The hard part is knowing what code to write.
-
-
-
Replying to @EricaJoy
Because low bandwidth organization around new products is difficult. We see drastic changes in efficiency when we get in the same room. Is it always required to be in the same room? Probably not, but it's harder to not be.
1 reply 1 retweet 24 likes -
Replying to @AustenAllred
So if I can reframe/rephrase your original tweet: Software engineers drastically underestimate how much easier it is to achieve organization around new products when everyone is in the same room. Does that feel right?
1 reply 0 retweets 12 likes -
Replying to @EricaJoy
Partially. Engineers think a company can just "go remote" and keep the same culture and productivity. If you want to maintain similar levels of productivity it takes a complete restructuring and rethinking of organizational behavior to make it work at all
3 replies 3 retweets 28 likes -
Replying to @AustenAllred @EricaJoy
The impression I get is that there are organizations that do remote very well because it's built into their culture and communication patterns, but organizations that weren't built that way initially can be hard to change.
3 replies 0 retweets 24 likes
That, and even if you start out remote coordination around building products can be difficult
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.