Even more simply: get good at doing things that could be useful in a number of contexts. You'll create a broad knowledge base to draw from, and be able to reapply existing skills in new ways/contexts.
Mostly my recommendation is that you become familiar with many different aspects of CS such that you can pick up something new if necessary. Example: get used to a number of documentation tools, so that if a company you join is using one, you have a relatively shallow learning curve, and already know what purpose such a tool would serve. Same thing goes for other tools like compilers, issue trackers, etc
I can only speak from the perspective of someone who has successfully entered the software development as a self-taught developer; I just finished my first year as an undergraduate, but I held a number of software development positions before electing to go to college. My education prior to working was varied, and the skills I now market center around my ability to quickly pick up a new tool/language/framework.
In computer science, a marketable skill isn't necessarily mastery/knowledge of a specific language, but rather higher-level skills you can apply and reuse in many contexts.
@StanShunpike "Does a cs course have to be in a marketable language to be of use?" In short, no. You can learn something marketable from any cs course, though you can also learn nothing from any cs course. The marketable skill won't necessarily be directly from the language, but might instead be debugging skills, a better understanding of machine organization, or other so-called marketable skills.
"Nature can also be ascribed value in religious frameworks: a monotheistic god creates the world, and either effectively declares it a work of art, or implies that humankind should assume the role of ruler. Casually, this remains an anthropocentric view, but it does so in the context of a higher power, thus making it monotheistic-god-centric view."