52 karma · joined August 31, 2015
The only thing is they're definitely not designed for regular consumers, you at least need familiarity with Linux networking.
They were paying me to work with this, yet they couldn't be bothered to fix this on their end.
What a terrible experience.
Well, watching a retired public school teacher get huffy and start chomping at your mother about how she's ruining her child can be a polarizing experience.
As for socialization, that was more than likely the most commonly voiced concern I would encounter. I'd get a lot of "but don't you wish you were with other kids?", and I would think "who the heck wants to be stuck with a bunch of kids?"
I've also been on on-site teams where only one or two junior devs work remotely. This always seems to work out poorly, but based on my observations it's usually due a combination of only being willing to only pay entry level rates, and failing to set deadlines for them. When we waited 4 months on a remote while he apparently just spun his tires on a simple bug, even after I explained the fix to him (it was ~4 lines, I basically said "try looking in X file on line Y, if you fozz the frob, does it fix it?") and he just like, could not. Also he'd have "internet issues" practically every day. Now the company is skittish about remote workers, even though it was obviously their own incompetence in managing him.
I know I personally do my best work when working remote, provided I'm not being pestered constantly. I just wonder if the "remote workers are bad" thing because it seems that many people seeking remote dev work are just starting out in programming or trying to transition from other jobs thinking those high paying computer programming jobs sound easy.
Here's a pretty enjoyable video about how they handled this sort of engine design problem using something sensible: https://www.gdcvault.com/play/1022186/Parallelizing-the-Naug...