The IBM 360 was on the market; third-generation computing was here! There was an insatiable need for computer programmers. If you had a college degree in ANYTHING, absolutely ANYTHING, and could pass one of those aptitude tests where they ask you what's the next number or word in this series and what would this pile of bricks look like from the back side, you were in.
I just got my degree in accounting and was looking at a starting salary of $400 a month. The university guidance counselor told me, "I just got this flyer from the municipal government for a job called 'EDP Trainee.' I have no idea what that means but you're qualified and it pays $625."
I ran down there, took the test, got the highest score they'd ever seen. The HR lady (they called it "personnel" in those days, we were still "persons" and not "resources" like toilet paper) wouldn't let me leave her office, she dragged me down to the computing center, waited for the boss to show up, and he hired me on the spot.
I spent two weeks in Cobol school, then started coding. My first program was never implemented. My second assignment was to make enhancements to a bread-and-butter application that was 3,000 lines long; that's a lot of punched cards. It took half a day to get the cards back from the keypunchers, an hour to compile, then another round of keypunching to correct your own errors, and overnight for a turnaround from operations to test the changes. We had a lot of time to goof off in those days.
I'm not sure that program ever went into production either. By then two years had passed and I'd received two pro-forma promotions and was making about $800. An absolute fortune when you could rent a really nice apartment for $200, buy a new Volvo for about $3000, fly from LA to San Francisco and back for $25, and go to a Creedence Clearwater concert for $7.50. My buddies who stayed in accounting were making $475.
I was one of the few people who could understand assembler language, so I was transferred into the systems programming staff. I wrote a special-purpose operating system for a mainframe with 32K memory, yelled a lot at the vendor's staff, and mostly helped programmers with their debugging.
Eventually I became a supervisor of systems programmers--back before the PC revolution did away with the supervisor position and there were actually people around to help you get better at your job. Then a project manager, finally an organizational manager (much better job if you ask me, I'd rather deal with two programmers who hate their boss than with a project that's six months late and a million dollars over budget), still in what was now called IT.
Then I bailed out of civil service, something to do with being smothered by a quasi-socialistic system and surrounded by people who were there because it was the employer of last resort. Stepped out into the wonderful, empowering, fulfilling world of the private sector and got knocked down, kicked around, run over, and spit on about eight times. Did a lot of training, always my favorite part of the job.
Still here, counting the years until retirement. I've done a lot of different stuff but it's all IT.