Before remote, the office was already increasingly hostile. Open floor plans, some groups having shared seating, and offices for roughly no one. Now, it’s worse. Everything is “reservable equipment” of garbage monitors, windows keyboards, and 400 dpi mice. I suspect it’s harder for a junior to succeed anywhere today vs 2012. The office is not built to foster development or innovation. It’s an exec’s idea of what a so…
IMO, an expensive keyboard/mouse/monitor isn't necessary for a junior to succeed. Plenty of coders learned on much worse.
How to set junior employees up for success in remote
41–50 of 370 posts
Re: How to set junior employees up for success in remote
#42Before remote, the office was already increasingly hostile. Open floor plans, some groups having shared seating, and offices for roughly no one. Now, it’s worse. Everything is “reservable equipment” of garbage monitors, windows keyboards, and 400 dpi mice. I suspect it’s harder for a junior to succeed anywhere today vs 2012. The office is not built to foster development or innovation. It’s an exec’s idea of what a so…
IMO, an expensive keyboard/mouse/monitor isn't necessary for a junior to succeed. Plenty of coders learned on much worse.
Re: How to set junior employees up for success in remote
#43Our company's new CTO held an all-hands meeting Friday where he stated something to the effect that he agreed with Elon (Musk) and that if it were up to him we'd all be huddled in the same office..."but times have changed". What I heard was "I really don't like that we can't keep an eye on you, but since the labor market is still so tight in tech, we have to deal with remote (for now)."
Re: How to set junior employees up for success in remote
#44Earlier quoted context omitted.
That's penny wise, pound foolish thinking. A good keyboard and mouse and monitor for your developers (who directly earn you revenue) is not going to break the bank. But the lack of them will reduce productivity and morale, possibly even causing (on the margin) some talented people to leave. RSI and posture problems are no joke! In other industries you need immense capital investment in equipment for workers to be pro…
It's a raindrop in a hurricane though, the best keyboard, mouse, and monitor in the world aren't going to make someone productive in an unproductive environment.
Re: How to set junior employees up for success in remote
#45Earlier quoted context omitted.
That's penny wise, pound foolish thinking. A good keyboard and mouse and monitor for your developers (who directly earn you revenue) is not going to break the bank. But the lack of them will reduce productivity and morale, possibly even causing (on the margin) some talented people to leave. RSI and posture problems are no joke! In other industries you need immense capital investment in equipment for workers to be pro…
It's a raindrop in a hurricane though, the best keyboard, mouse, and monitor in the world aren't going to make someone productive in an unproductive environment.
Engineers are expensive, and every minute they spend fighting with equipment rather than being productive is costly.
Re: How to set junior employees up for success in remote
#46But some of my best jobs were not like that. They were sitting down with people in very up close conversations and working out ambiguities and tasks. And mentoring juniors and working things through with them.
All that said, I won't be going back to in person. I'll be hunting for places that know how to make remote work, even though I don't prefer it. Because remote is still better than the 1.5 hours a day I was spending driving and the toll that was taking on my health and sanity. And most of the local employers are crappy.
So it's a real mix of stuff, we're in a transition period. It's going to take a few years for this stuff to shake out.
Re: How to set junior employees up for success in remote
#47Question for anyone who's had to onboard/train Jr's in a 100% remote environment, what's worked for you? How do you maximize their chances of success? What are some common pain points? This has been an issue at my org and we're having a hard time improving it.
Maybe a better online solution would help, a-la some magical VR space that Meta comes up with.
Re: How to set junior employees up for success in remote
#48Before remote, the office was already increasingly hostile. Open floor plans, some groups having shared seating, and offices for roughly no one. Now, it’s worse. Everything is “reservable equipment” of garbage monitors, windows keyboards, and 400 dpi mice. I suspect it’s harder for a junior to succeed anywhere today vs 2012. The office is not built to foster development or innovation. It’s an exec’s idea of what a so…
IMO, an expensive keyboard/mouse/monitor isn't necessary for a junior to succeed. Plenty of coders learned on much worse.
Re: How to set junior employees up for success in remote
#49For junior engineers it's really easy to fall into the trap of trying to solve everything themselves instead of asking for help when they are remote. I say this as somebody who has spent the last five years working remote team-based gigs.
That being said I think it can probably be improved while still remaining WFH, for instance by more actively chaperoning newbies.
Re: How to set junior employees up for success in remote
#50Earlier quoted context omitted.
That's penny wise, pound foolish thinking. A good keyboard and mouse and monitor for your developers (who directly earn you revenue) is not going to break the bank. But the lack of them will reduce productivity and morale, possibly even causing (on the margin) some talented people to leave. RSI and posture problems are no joke! In other industries you need immense capital investment in equipment for workers to be pro…
Your comment reminds me of all the people screeching about their good school district, as if it is somehow capable of covering for them if they choose to be a crap parent. In both cases the stuff people are fussing over is basically a rounding error compared to the big factors. Beyond some basic utility, e.g. being able to compile the code in under 5min, the hardware one uses is of negligible impact to their success.…
It can break my god damn wrist joints if I have to use it all day. Speaking from experience.