Should I do the physics version as well?
I am fairly certain that you will use basic addition / multiplication in everyday life without having to be a maths expert, and have it be useful, even essential to you.
Anyway, nice strawman argument you are creating. On you go with the physics one.... (funnily enough I don't find myself using my school pyhsics in everyday life the way I use maths)
I took a couple of basic physics classes well before I went to university. The stuff they teach you is not especially useful. Elastic and inelastic collisions, deceleration from friction, F=ma. It's easy. Learning to model large systems is a lot more difficult, and that requires at least some experience that you aren't going to learn in a beginner's physics class.
I expect there are a lot of people who benefit from the lesson that computers do things in a certain order (I realize that this isn't necessarily true...).
I agree with the OP. It's important to learn system administration before programming. Know your environment.
Writing markup is fine and will help you understand what's going on when you view page source, but it's hardly the enlightenment you make it out to be.
I really can't understand how anyone who does sysadmin work and any amount of programming can say this.
My mastery of computers grew organically. I started out with "power user" stuff. Namely, tweaking my computing environment (Windows, at the time) to my liking. As I tweaked, I inevitably broke things, which meant I had to learn to fix them. It wasn't long before I realized that being able to fix computers when something goes wrong was a valuable skill, so I developed that skill further.
I had a friend who wrote simple programs in VisualBasic from around the time that Windows 3.1 came out. He wrote a baseball card database application that we both used to catalog our collections. From that, I understood the utility of programming as a means to solve problems that were imporant to me, but I was too consumed with other things. It wasn't until the internet gained popularity that I started to write programs. What I'm getting at is that I was late to the game. I was in to computers for a long time before I had much interest in programming.
My skills as a sysadmin were pretty decent to begin with, but I became a troubleshooting superman as my programming skills developed. It literally changed my entire perspective, and even my methodology, when troubleshooting. I could read a stack trace! I could load up dump files, import symbols, and dig around to find the offending file, which would lead me to a specific application or a device.
Even at a very basic level, learning to program taught me a tremendous amount about how software works. Those insights led me down the correct paths when working as a sysadmin. I began to understand not just what to do, but why.
I used to think like you, I don't anymore. We (Axiom Zen) co-organized the HTML500, Canada's largest free learn-to-code event. In one day, 500 people came together and learned the very basics. The response was overwhelming, check it out for yourself: https://twitter.com/search?q=%23html500
These folks are looking with totally fresh sets of eyes at what you and I take for granted. Learning the basics gives them the same appreciation you and i have for the abstractions that can be built on top.