5 ms·
> Feedback in general doesn’t benefit from in-office scenarios in my experience, so long as the junior is proactive. In your comment you say you haven't worked
by returningfory2 3y ago
> Feedback in general doesn’t benefit from in-office scenarios in my experience, so long as the junior is proactive.
In your comment you say you haven't worked in-office much. So, genuine question, how do you know feedback doesn't benefit from being in-office?
I think this relevant because in my experience (1.5 years remote because of COVID), the benefits of being in the office often aren't apparent when you're out of the office. For example, in work I regularly overhear O(2 minute) conversations in which co-workers talk about edge cases in our system that I didn't realize existed. If I wasn't in the office I wouldn't even know I had missed these conversations.
- BlargMcLarg 3y ago>For example, in work I regularly overhear O(2 minute) conversations in which co-workers talk about edge cases in our system that I didn't realize existed Counterpoint: there are types which really like to insert themselves in every conversation or discussion. To the point it hampers not just their own work, but the work of everyone else. Taken to the extreme, they even create a state of helplessness in others, where these individuals become a funnel for all others to ask questions and obtain knowledge from. This is without accounting for all the noise pollution it creates. Opponents are very eager to pull out these 'what about the office talks?' arguments, but whether the benefits even outweigh the downsides isn't obvious at all. Heck, most developer work cultures use Scrum, and they can't even work through a single item on their retrospectives. Surely a bit of skepticism is warranted.
- tivert 3y ago>> For example, in work I regularly overhear O(2 minute) conversations in which co-workers talk about edge cases in our system that I didn't realize existed > Counterpoint: there are types which really like to insert themselves in every conversation or discussion. To the point it hampers not just their own work, but the work of everyone else. That's not really counterpoint, it's just a occasional problem behavior of some individuals that remote makes more difficult, like someone humming at their desk. It's sort of like someone who writes a bunch of useless unit tests. The solution isn't for the team to scrap unit testing, it's for that person to be coached to not do that. One big problem with remote is that it makes a whole lot of stuff that can happen organically in an office into intentional practices that require discipline, which means they're a lot easier to neglect.
- BlargMcLarg 3y ago>That's not really counterpoint, it's just a occasional problem behavior of some individuals that remote makes more difficult Yet anecdotally, it has occurred in every open office so far. Managers were also eager to applaud this behavior rather than berate it, while at the same time looking at the actual work performed, scratching their heads why nothing was happening and then giving said individuals special treatment. I'm not alone in experiencing this, either. >One big problem with remote is that it makes a whole lot of stuff that can happen organically in an office into intentional practices that require discipline, which means they're a lot easier to neglect. "That's not really a counterpoint, just coach them not to do that." If your argument against my point is 'well just teach people differently, also it doesn't happen that often at all (despite it being a common complaint on the internet)', you'll also have to argue why your point is special enough not to deserve the same response. Companies relying on a lack of documentation and individuals using said documentation is a humongous risk even outside the remote debate, and that's most of the requirements for remote covered. Those 'organic intentional practices' don't seem so great when 80% of the seniors on the team leave without a paper trail and the remainder knows zilch.
- tivert 3y ago> Yet anecdotally, it has occurred in every open office so far. Open offices are terrible, by the way. They provide few benefits, and their main effect is to magnify the downsides of in-office work (at least for software development). They just happened to be trendy and enable lower real-estate costs. > Managers were also eager to applaud this behavior rather than berate it, while at the same time looking at the actual work performed, scratching their heads why nothing was happening and then giving said individuals special treatment.... you'll also have to argue why your point is special enough not to deserve the same response. Many managers are not great. A busybody is undermining team productivity without adding value is a management problem focused on that individual. Remote work introduces more systemic communication and training problems. > Those 'organic intentional practices' don't seem so great when 80% of the seniors on the team leave without a paper trail and the remainder knows zilch. My experience is remote work isn't leading to any special emphasis on documentation. And in any case, any reasonable level of documentation isn't going to make up for all the experienced people leaving.
- bart_spoon 3y agoI worked in-office for about a year and a half. Then I switched fields and companies right before the pandemic hit, so I was effectively starting over again. I did not find being in-office vs remote to be particularly impactful on my ability to be effective, get feedback, and get up to speed. Obviously this is a very small sample size based solely on my personal experience.