Comp. Scientist
I.E. Building them better, faster, stronger
That's more of a job for the electrical and computer engineering fields than computer science. If you meant the physical hardware side of a system that is.
Honestly, programmers are a dime-a-dosen work force nowadays. You need to find one thing that separates you from every other programmer and makes you indispensable, otherwise you probably won't get a job. Experience also helps with this. The more projects you've worked on and the languages you've learned, the better off you'll be.
For employability, it's important to know both specific programming skills and know the theory behind software systems design. You can be a code monkey in a specific language and churn out working programs all day, and you can get a degree in computer science without ever really learning proper programming design and techniques.
Knowing a ton of different languages isn't so important compared to knowing the workings of different programming paradigms (e.g. procedural, functional, and object-orientated). If you have a strong knowledge of how a language works and why certain design choices were made you can easily switch to other similar languages as at that point you only need to know the syntax of whatever language you choose.
You can learn a lot in school, but I see academic education as just the training to start thinking like a professional in your field of choice. I've learned more working on projects and internships than I have sitting in classes, but the classes gave me a strong foundation to further my knowledge.
I'm employed in my first software development role right now and while I really enjoy the work, it can get quite difficult and downright frustrating at times. If you choose to pursue an education in computer science or some sort of programming you most likely won't end up designing
VIDEO GAMES for a living. Video game design, while big, is an over-saturated market and makes up only a small part of the world's demand for software development. There are still many interesting challenges and projects to get involved in besides just video game design though.
And of course, you always run the risk of getting shoved into a role where you do nothing but maintain poorly designed corporate dinosaur code running on a language no one has used in 40 years running off some 1981 IBM mainframe barely held together by duct tape in the year 2017. Death doesn't come quickly enough for those poor souls.
tl;dr
Programming sucks fat dog balls.
