Don't get me wrong, everything in Pillar #1 is important, but I think there are much more important things for an aspiring developer to consider.
Just off the top of my head:
- program structure and organization
- variable typing, naming, & use
- function/subroutine strategy & use
- frameworks & APIs
- algorithms
- database design, structure, & access
- benchmarking
- performance tuning
- scaling
- security
- testing philosophy and strategies
- systems analysis
- systems design
- prototyping
To better understand the difference between a software developer and a systems administrator, I often use this analogy:My users/customers are race car drivers. We developers build and maintain their cars. Systems administrator build and maintain the racetrack itself. Every link in the chain is necessary, but in my experience, smooth pavement with poorly running cars is the norm. So we developers need to focus more on building better software and leave as much admin as possible to those experts.