Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I have hard time explaining exactly how our async way of communicating makes the whole wfh situation so much more pleasant (we work via GitHub) to my non-developer colleagues. I feel they could benefit a lot and their constant complaining about telco filled days could be much reduced. But how could they do this when they email office docs around (i.e. for grant applications or IP) and fill out bespoke systems for their project management steps...?


Shared docs (e.g. GSuite or Office365) help. I rarely mail around documents. And even to the degree that you also have calls, a shared Agenda is a good start.

Personally, I don't much care for using things like Trello or GitHub for non-software tasks and generally resist doiung so.


I push for those, but some people lost some data because at point OneDrive just decided it would incorporate someone's desktop folder (seriously, why?!). And occasionally it errors with cryptic error messages like "can't open document" no further info. People fear it and I understand them actually. It must really be flawless, mess up 3 hours of work for someone and it will take years before you can try and pry them away from email-only again.


It will never be flawless.

But it could be like git, recoverable.


I actually don't have any real experience with Microsoft's cloud products, just Google's. They're pretty flawless IMO and have just the right set of features for me in general. Certainly I've lost far more work over the years with desktop products crashing or just accidentally deleting the wrong file.


Initiatives, Epics, Issues, Tasks and Subtasks.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: