I’ve always been an op, not a coder: I could pound on a DECwriter, I could change a ribbon on some arcane IBM printer like the 4214, and when called upon, I could speak some pidgin version of VAXese. But I remember these days frighteningly well:
The last time I went down this road I wrote my own search function that would return the element with the closest value to my requested target. I also wrote my own insert and delete routines. I did this because when I went to school everything about computer programming was about saving CPU cycles. Beginning programmers got seven seconds of execution time on the mainframe. I screwed up once in a junior level class and burned my entire semester’s allotment before the OS kicked me off. That rated some words from my professor.
I wonder why it took me so long to figure this out. I’m thinking it might because most of the programming work I did involved making things work, and there was no end to it. Well, I guess it did come to an end which is why I am unemployed. Computer companies eventually got their acts together and started building machines that worked when you turned them on, and software companies started producing software that people could use to do something useful. Took a while but they eventually got it sorted.
I got a reminder of this last week when I ran an optimization cycle on the database that underlies this site. Cut the size from 125 MB to 121. And I remembered my very first hard drive, which would hold almost one-sixth of that database — reluctantly.