|
|
|
|
|
by christophepas
1456 days ago
|
|
Founder of Slite here, your reply is spot on, we try to be as honest on the pros and cons of remote when we think internally of the future of this market, and when we share our research or insights outside. It's not all pink, and our mission is very much to remove the roadblocks, so we need to acknowledge the issues that prevent remote from being seen as a no brainer
by some teams today. |
|
I'm a bit older and I couldn't imagine going through this as a fresh grad out of college. I would have loved to have had my hand held in my first days as a dev. I was constantly demoralized by not having the domain knowledge (and not having any comprehensive documentation to learn it), being assigned complicated stories (that even the mid/senior devs had trouble with), and by not having anyone just regularly check in with me and make sure I was doing ok. I would like to continue working remote indefinitely, but man it was really tough starting out as a dev remotely. I say all this to say I do think it's possible to successfully onboard a new dev remotely, but there has to be a plan and resources available to do it and I think your article is a good template.