One criticism: I believe that the majority of programming jobs are software engineering jobs (even if that's not in the job title). Since many are using CS as prep for programming careers, I believe this list may need more emphasis on software engineering and contemporary skills and knowledge in SE.
For example, I saw testing in the advanced section if I remember correctly. But it was one of multiple options I think. Doesn't everyone need some testing knowledge/experience?
Another one is requirements analysis or negotiation. Figuring out _exactly_ what needs to be done, in a way that makes complete sense all the way through, is feasible and high priority, isn't nonsense from a UI or database perspective, and getting the other people to go along with that, is pretty important to most programming jobs I have had.
Another example: back in the good ole' days of CS, large scale code re-use may have been mostly a dream for most popular programming language ecosystems (that weren't Perl). But now, even though dependency reduction still seems much cooler, being able to use real package management systems and select the right modules or components is critical for most jobs. Not sure that type of thing gets quite enough attention in this list.
In my experience, at my school testing is done to pass a professor's designed test cases. Usually you don't know the professor's test cases in advance.
One criticism: I believe that the majority of programming jobs are software engineering jobs (even if that's not in the job title). Since many are using CS as prep for programming careers, I believe this list may need more emphasis on software engineering and contemporary skills and knowledge in SE.
For example, I saw testing in the advanced section if I remember correctly. But it was one of multiple options I think. Doesn't everyone need some testing knowledge/experience?
Another one is requirements analysis or negotiation. Figuring out _exactly_ what needs to be done, in a way that makes complete sense all the way through, is feasible and high priority, isn't nonsense from a UI or database perspective, and getting the other people to go along with that, is pretty important to most programming jobs I have had.
Another example: back in the good ole' days of CS, large scale code re-use may have been mostly a dream for most popular programming language ecosystems (that weren't Perl). But now, even though dependency reduction still seems much cooler, being able to use real package management systems and select the right modules or components is critical for most jobs. Not sure that type of thing gets quite enough attention in this list.