issues facing computer science majos
Issues Facing Computer Science Majors After Graduation
EJ
10/9/2013
[Type the abstract of the document here. The abstract is typically a short summary of the contents of the document. Type the abstract of the document here. The abstract is typically a short summary of the contents of the document.]
Most career paths in computer science involve people skills and interacting with people. Beyond an entry-level position as a software engineer, almost any corporate position requires working with people. The creation of software is most often a team effort, and software companies are organizations of people like any other type of company. Thus, if your career path is typical, you will not be alone in your cubicle staring at the screen.
Chances are, it will be peer/family driven. Personally, my brother was the one who encouraged me to take a computer science class. I had tried to learn how to code before, but was so unsuccessful that I couldn't even set up the development environment. Even though he dropped out of his intro CS class, he told me that I could do it and that the field needed more women engineers like me. Through his faith in me, I took a web development course and jumped on the intro CS track at Stanford, and have stuck on the CS train ever since. It's easy to give up. It's easy to give up and say, oh, who cares, someone else will code it for me. Another one of my awesome CS Professors, Eric Roberts, showed us on the first day of my second introductory class that even if Stanford graduated all of its students as CS majors, and the Valley hired all of them, they'd still need more people to fill the jobs. It's not surprising that software is where the jobs are, and even working for eBay, talent is one thing that the company is aggressively looking for. You can give up, but what about what could be? Maybe you could code the next app
Experimentation is key. Learning CS involves experimentation. You have to mess around with the
EJ
10/9/2013
[Type the abstract of the document here. The abstract is typically a short summary of the contents of the document. Type the abstract of the document here. The abstract is typically a short summary of the contents of the document.]
Most career paths in computer science involve people skills and interacting with people. Beyond an entry-level position as a software engineer, almost any corporate position requires working with people. The creation of software is most often a team effort, and software companies are organizations of people like any other type of company. Thus, if your career path is typical, you will not be alone in your cubicle staring at the screen.
Chances are, it will be peer/family driven. Personally, my brother was the one who encouraged me to take a computer science class. I had tried to learn how to code before, but was so unsuccessful that I couldn't even set up the development environment. Even though he dropped out of his intro CS class, he told me that I could do it and that the field needed more women engineers like me. Through his faith in me, I took a web development course and jumped on the intro CS track at Stanford, and have stuck on the CS train ever since. It's easy to give up. It's easy to give up and say, oh, who cares, someone else will code it for me. Another one of my awesome CS Professors, Eric Roberts, showed us on the first day of my second introductory class that even if Stanford graduated all of its students as CS majors, and the Valley hired all of them, they'd still need more people to fill the jobs. It's not surprising that software is where the jobs are, and even working for eBay, talent is one thing that the company is aggressively looking for. You can give up, but what about what could be? Maybe you could code the next app
Experimentation is key. Learning CS involves experimentation. You have to mess around with the