I like this editorial. What I like even better is how I saw it differently to a degree than anyone else. The first word that jumped to my mind when Steve said using resources most efficiently was "spaghetti". Often in the old days the most efficient code was rarely readable and understandable. People avoided calling subs/procedures because they took up extra memory when a simple yet devastating GOTO would do the trick. I know that once I had to do a material safety process and I only had 32k of memory to work with. Wow was it ugly code but it worked and fit into the limited memory (that included storing the data sheet). I remember when we had to upgrade it when memory limits were removed, I was definitely badmouthed! 🙂

I'm thinking the most efficient code may not always be the most elegant code.