Programmers without computers

Original author: John D. Cook
  • Transfer
When I first started working as a programmer, I was surprised at how much my colleagues can sit at computers. Of course, the programmer needs to spend a significant amount of time sitting at the computer, but why do you need to spend 100% of the work day at the monitors? It seemed rather strange to me because I had never worked in this mode. I always alternated thinking about some ideas outside the workplace and sitting directly at the computer.

I was even more puzzled when the network fell, which happened quite often. Half worked on a Windows PC, the other on Unix workstations. When the network crashed, PC owners continued to work because they had local work environments.

At this time, Unixoids crowded in the lobby until the network rose again, or even went home if it was not expected in the near future. They had computers in their places, but they were mainly used as terminals for connecting to servers. That is, when the network fell, Unixoids were left without computers. Everyone agreed that this meant that work could not be continued. It seems strange to me.

At that time, I knew how to program, but I knew almost nothing about professional software development. Most of my ideas were naive. But looking back, it seems to me that I was right in one thing: programmers should often think with their own head, moving away from the computer. Unfortunately, in most cases we do this last .

Also popular now: