My career has been almost entirely surrounded by or involved with computers in some way or other. Early in my career I programmed greenscreen apps in COBOL. There really wasn’t ever much downtime, because whenever for some reason I was in a holding pattern on my primary assignment, there would always be some collateral project I needed to work on. When I frst transitioned into IT, I was still officially a subject indexer and had indexing work to do alongside. I should point out that this period in my career was spent in small companies which did everything that needed to be done, themselves.
Later I was at a huge pay TV company where minute division of labor and outsourcing were the hallmarks. When it isn’t possible to get anything done without getting Denver, Manila, and Bangalore on a conference call, you’re more apt to find yourself in an idle situation. Especially if if it’s the sort of company where you get called on the carpet for approaching the wrong people with a question. Some people can thrive in that kind of environment, but they are generally not the traditionally stereotypical computer geeks. Those people can fail miserably. So I’m told, but of course I wouldn’t know anything about that.