I would disagree, that operating a computer or computerized system is not necessarily being computer savvy. That is what the author is trying to say. I have lo

I would disagree, that operating a computer or computerized system is not necessarily being computer savvy. That is what the author is trying to say. I have long felt that when you have experienced the lower or lowest levels of abstraction, even in archaic times, you develop an intuition about how a thing works or how a problem might be fixed, or how to properly scrutinize or be suspicious of a particular new form of tech (itself often implemented at these higher levels). One example would be diagnosing "bad internet" by evaluating the wifi signal strength & interference from similar channels, the cable/fiber modem basic functionality and firmware version, the cable quality and function, the networking card in the computer, the function of the software behind it, the browser behavior, caching, or getting "wedged" somehow, the DNS resolver or its cache, an OS bug... it goes on and on. The flip side of this is: everything is fricking multilayered and complicated! And it sucks! But that's unfortunately what we've got when you have so many layers involved. Disclaimer: I'm firmly in the demographic described in the article.