4 ms·
I work across 12+ hour time differentials quite often. The real keys are independence, trust and working on projects where touching bases weekly or so makes se
by teunispeters 7y ago
I work across 12+ hour time differentials quite often. The real keys are independence, trust and working on projects where touching bases weekly or so makes sense - and otherwise operating over email.
(that last is the biggest key really).
I'm a software developer and the teams mostly coordinate over code feedback and ticket requests anyway.
- somethoughts 7y agoYes I can definitely see it working super seamlessly for something like GitHub/Gitlabs and other tools that are for SW developers built by SW developers. I feel like for stuff with UX or stuff that requires significant collaboration that can't be done via git comments, someone needs to take the hit to be up at odd hours for real-time discussion meetings via Zoom/Skype or make other such work-style adaptations.
- teunispeters 7y agoI'm pretty much full stack - UX work is typically "post a prototype or sketch or plan, wait for feedback". I think this works better when one has strongly structured design protocols though. I've worked through a lot of different fields getting to where I am now - for instance, warehouse inventory and paperwork handling raises the importance of accurate warehouse inventories (and they weren't low before) - but a lot of the paperwork could easily be done remotely these days. (sometimes I miss forklift driving - it was a lot less stressful than programming in many ways, although it required a much more immediate care and caution and physically higher risk) I suspect that crosses a lot of other varieties of work - paperwork could be more offloaded or moved digital, while the key actions still require people, mostly. And someone always has to maintain the infrastructure.