Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

One thing I have noticed is that while the old hats (those hired some time before the pandemic) are as productive, or maybe even more productive while working remote, it's a struggle to bring in new people, especially more junior people. Maybe these are problems that can be solved, but it seems that an already a challenging and stressful situation, joining a new company, is even more difficult when you are not able to spend time together in person to pick up on team dynamics and just general mentoring.

I assume it's a bit easier if you are more senior and have a few company changes on your resume, but for someone for whom its their first or second job in the industry, it can be overwhelming. I think that's why often fully remote companies pre-pandemic seemed to be more focussed on hiring seniors.

Likely some of these problems can be mitigated as we learn how to deal with them, but this is one reason why I think post-pandemic most software houses will have to adopt a policy of encouraging some on-site work.



I have joined a company remotely and I don't feel I got slower productive than before. The ability to do pair work is almost enhanced and the fact that everyone is able and willing to be called in to help has accelerated learning and integration in some areas which I found harder in the past.

Also keep in mind that it may be slower than with direct in person mentoring but there can also be the opposite of in person mentoring and then being locked in the same office can become extremely stressful.

I also run a small team with new hires on one day and I'm seeing great productivity and teamwork.

We are going back to the office eventually but I don't think the on-site requirements will be as strict as in the past. In the medium term I see us moving towards a more flexible model beyond just the flexible allocation of desks (which imho. is a horrible thing, pretending to be office workspace and serving neither then needs of people there nor the companies output).


Off-topic, but how do you feel about pair programming?


not that guy, but the two times I've had to do it I was miserable. I like getting an assignment and then going off to my cube to do it. To have to constantly be in communication with someone makes my work miserable. I'll gladly send you status at the end of the day, just don't make me ever work that closely with someone again or I'll find a new company.


I never had a job where I did but it happened sometimes (eg solving a critical problem together, or pair programming in new projects to learn). I found it hugely stressful: it made me anxious to have someone waiting for me to collect my thoughts, and work twice as tiring.

I would probably refuse some a new position if there was the expectation of constant pair programming, but I'm curious if others have different experiences.


"One thing I have noticed is that while the old hats (those hired some time before the pandemic) are as productive, or maybe even more productive while working remote, it's a struggle to bring in new people, especially more junior people."

My employer has always (started in 2007) been fully remote; we've never had office space ANYWHERE. It's a small team building a relatively niche product, and we're pretty successful, but what you say is true:

Getting new people up to speed is hard. And hiring "baby developers" is just not something we've done. All our hires are midcareer or later. I feel like a fresh dev needs the office environment to get traction early in their career, and we just can't provide that.


I did notice something similar. We brought on one junior last year and I had to schedule about 5 in-person days with him to do actual pair programming to teach him some stuff. That said, I think what stopped me the most with being productive over video chat was not being able to point at his screen and had to describe in detail when I wanted him to look at something. Giving people a virtual pointer to point at stuff on the presenter's screen would be welcome.


Pair programming all day long is a decent solution to that problem




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: