3 ms·
Yep, I've been 100% remote for 5 years now (wow, it feels weird to see that number!) and am never going back, for the same reasons. The only caveat is that it'
by imsofuture 10y ago
Yep, I've been 100% remote for 5 years now (wow, it feels weird to see that number!) and am never going back, for the same reasons.
The only caveat is that it's important that you work in an organization that is aligned with remote work, if not remote-first. Just scoring 'permission' to work remotely somewhere not used to it, is probably a recipe for a pretty bad time.
- ylhert 10y ago5 years is a long time, I'm sure you've got some great experience on the subject, would love to read more about your experiences! I really agree with your caveat, and I've seen a number of places that have some pretty unmotivated individuals try it, and have it fail. This left a bad taste in everyones mouth, and they wrote off remote work. The reality was that they had crappy employees, and not that remote work can't work.
- lacampbell 10y agoJust scoring 'permission' to work remotely somewhere not used to it, is probably a recipe for a pretty bad time. Why is that?
- ghaff 10y agoBecause the processes and mindset won't be setup for it. Decisions will get made in hallway conversations or even in meetings in which no one thought to send out a phone number for the remote employee to attend. Hence the idea that remote working is probably most effective when companies treat it as the norm--at least on a group by group basis.
- lacampbell 10y agoRight. I've actually never worked at a place with a large number of devs under the same roof.