3 ms·
> And my experience is simply the opposite of yours. We keep talking past each other. This is the last reply I'm going to make, but hopefully it will add somet
by timr 4y ago
> And my experience is simply the opposite of yours.
We keep talking past each other. This is the last reply I'm going to make, but hopefully it will add something: please consider that your experience is not opposite of mine, but instead, that you haven't run into the problems yet.
Maybe, for all of your success and advancement, you haven't yet reached the limits I'm talking about. Just consider it.
- broast 4y agoFair enough I'll also ask that you consider the possibility that you haven't experienced overcoming this limit yet. After all, what do we need to learn about our work that can't be represented as text Or that this limit might be qualitatively different for different people, and that some people are better at online text-only relationships than face-to-face ones. Our teams may have faced limits in real life that only got solved by going remote. (For example, I do believe that when we were in person, we wrote lower quality software, less well-tested, with less communication and collaboration, at a much slower pace, than we do now (you can imagine why - likely we used to rely on informal processes more than we thought or wanted to)) I did mention that I've seen other teams (anecdotally, on less technical areas of the product) face problems with being fully remote- but that was usually fixed with staffing... or a remote leader inheriting the team... We've had many people in our org exclusively remote for the last 20 years as well - these people became the remote leaders on our teams and led by example. It all depends on the remote fit.