|
|
|
Ask HN: Backup plan(s) for a CS major?
|
|
18 points
by zupancik
4617 days ago
|
|
I'm an undergrad at UC Berkeley, and the reason I chose it was for it's outstanding EECS program (electrical engineering and computer science). However, there are lot of people back home and in other places who view the current demand for programmers as a "tech bubble" and they don't expect the "dreams" of Silicon Valley to last. I know programming itself will always exist, but how do I adapt as/if the bubble collapses? Any suggestions on other career paths that would find my CS experience valuable? I love programming in itself, but I don't want to regret my major choice because I blindly followed the crowd with no backup plan. |
|
1) The career of programming (specifically) has MANY options which are not concentrated in the tech bubble. I know that is not obvious being so close to the epicenter of it, but 90%+ of professional programmers work, in Silicon Valley parlance, boring companies doing boring things. Banks gotta bank, insurances companies gotta insure, logistics companies have to do something without any convenient verbs to describe it, and all of the above hire (or beneficially hire, via staff arrangements with companies that are uninteresting to the Valley) vast numbers of programmers.
2) The ability to program doesn't hurt your suitability for virtually any type of knowledge work (when compared to a BA/BS in an unspecified field from Berkeley). Most of the time, it will help you, since it gives you superpowers with regards to many tasks you might be expected to do. In my (brief and unlamented) stint as a translator, I shaved months of mind-killing drudgery off my schedule because I have superior options for getting Japanese from Word documents into HTML than copy/pasting one line at a time into Dreamweaver. You may find yourself working in a job which involves analysis or acting upon data, a task at which worksmanlike command of a single scripting language makes you a hero worthy of legend. You will find, for example, that many companies still generate e.g. monthly reports by having people manually collate/screen-scrape-with-their-eyeballs six different data sources into an Excel file which is version controlled by copying with creative filenames onto a shared directory. You might think that somebody capable of programming their way out of a paper bag could do a better job in two day's of work. Some times, you're not wrong.
3) Even if you don't do programming on a day to day basis, knowing how to get what you want out of computer systems and computer people is valuable. Smart people often suck at this. You being a bridge between those smart people and their captive techies can make you indispensable. (For example, I bet Obama would currently kill for one person in his inner circle who can tell the difference between frontend and backend at the moment. That sort of opportunity exists in a lot of places.)
4) Your major matters much much less to your career path than you have been socialized to think, because you have probably not talked career paths with many people outside of academia, who have very skewed views on the matter. Three years from now nobody will care what you studied in undergrad.