These kinds of checklists tend to reveal the bias of their authors.
If I were authoring one I'd have a bunch of stuff in there about understanding the hardware, performance, caching, power consumption. How the compiler produces the instructions that actually run on the machine. A bunch of the how's and whys of the various OS designs and how that affects the problem in front of you might go well in there too. And so I reveal my bias and I'm probably overlooking something quite important that's your particular strength that makes you really great in your programming niche. At least I'm aware of it, which neither of these guys seem to be.
I agree. I should have said: "This checklist helped me a lot, after getting a masters degree, as a starting point listing the general aspects to get to know in the particular professional path that I'm currently following". If CS was my world, that checklist would be a map of the country I'm living in at the moment (or even better: a travel guide).
If I were authoring one I'd have a bunch of stuff in there about understanding the hardware, performance, caching, power consumption. How the compiler produces the instructions that actually run on the machine. A bunch of the how's and whys of the various OS designs and how that affects the problem in front of you might go well in there too. And so I reveal my bias and I'm probably overlooking something quite important that's your particular strength that makes you really great in your programming niche. At least I'm aware of it, which neither of these guys seem to be.