DEV Community

Discussion on: I've been a programmer for over 20 years, watched the internet the grow up, ask Me Anything!

Collapse
 
jfrankcarr profile image
Frank Carr

Working remotely was more possible early in my career than it was in the middle part.

In the late 80's to early 90's, shared network resources, like databases, weren't common in the PC world. This was the area of mainframes for the most part and PC apps were largely standalone and databases were local. If a developer had a laptop (very expensive and underpowered in those days) or a luggable they could work at home. My first work development system was an IBM PS/2 Model 70 Portable. While my employer at the time didn't want us to work from home on a regular basis during the work day, we were expected to work at home at night and weekends from time to time. Other people I knew had more flexibility.

Once networked databases became common, working at the office became necessary since most companies did not want to invest in the infrastructure for remote developer access and most developers only had dial-up internet at home. This often meant long hours in the office, trying to complete projects.

Starting about 2003-2005 or so, remote work became more common, not much different than it is now.

What mistake do young developers make frequently? Assuming that they already know everything and not getting in sync with development team. Really, it's the same mistakes senior developers will often make when coming into an established team.