Sharing mostly as a "devil's advocate" post. I fully support WFH (I've been doing it for 10+ years), but curious to see discussion around this article and the effects it has on junior engineers, and -- more importantly -- maybe some solutions folks have seen work to overcome this for junior devs.
> Acceptable for a seasoned employee to ask an informed, targeted question, but probably more work than its worth for a less confident junior.
Sorry, my solution would be to hire better juniors.
An unconfident, but literate, junior can also succinctly pose questions.
Even with in-office teams, whenever they are global and hence de facto async, literacy is crucial.
[so maybe this is too strong: can anyone think of an engineering colleague whose work they think of as excellent, yet can only collaborate synchronously? I wrote the above because I can't]
This doesn't matter as long as you plan on milking it forever. Of course, that does leave a lot of ladders on the roof and you don't want to be alive when the technopocolypse happens.
5 comments
[ 0.27 ms ] story [ 24.9 ms ] threadSorry, my solution would be to hire better juniors.
An unconfident, but literate, junior can also succinctly pose questions.
Even with in-office teams, whenever they are global and hence de facto async, literacy is crucial.
[so maybe this is too strong: can anyone think of an engineering colleague whose work they think of as excellent, yet can only collaborate synchronously? I wrote the above because I can't]