Can you share your stories around how working remotely in the 90s was like?
e.g. there probably wasn't video chat. So how did you communicate? Were you coding? What were tooling like for coding remotely back then? etc etc
e.g. there probably wasn't video chat. So how did you communicate? Were you coding? What were tooling like for coding remotely back then? etc etc
I worked at the end of a Telebit Trailblazer, so I had a 19200 baud link to the internet. I remember emailing myself GCC - staged the tarball on a remote host, uuencoded it and sent it home as multiple email messages.
We mostly did stuff via email, with the occasional conference voice call. I had to learn to restrain myself and not try to solve user problems when I first saw them - because of the distribution of time zones, I would tend to be the first person awake.
This was definitely coding - we were selling and supporting Interlisp-D and its many derivatives.
When I worked for other people, management spent a lot of time with requirements and specs before implementing, which often resulted in mismatched software expectations. Agile gets poo-poo'd now, but it was a revolution at the time
When I was doing my own consulting, I always did my best to find local clients for remote work (often building e-commerce web sites when the competition was still using FrontPage) because it was preferable to be able to call the client or meet in person to discuss the inevitable requirements snafus.
Honestly, it doesn't seem that much different now. Humans are generally not all that great at communication. The tools we have today make a dent in that problem but there's still significant unresolved challenges.
When I'm leading teams, I tend to spend a lot of time on teaching people to communicate more effectively and creating processes to enable it. It makes things go more smoothly than trying to be the central hub for all communication.