This is a response to/continuation of a story by Arthur Shi that really resonated with me, but after thinking it over a bit, I disagree with parts of his piece.
When I started studying computer science (CS), I’d wanted to be a middle school math teacher for most of my life, but was by no means a STEM person. I preferred the Humanities, but found parallels between writing a story and writing code. It’s also neat that, if you have an idea, you can build something (anything) that people will use. Even if you don't know how, you can learn.
I’ve met so many hardworking, passionate, creative, intelligent, and all-around amazing people, and have experienced educational opportunities like Twitter Early Bird Camp (shown in the picture below), Square Code Camp, various hackathons and conferences), professional roles (two-and-a-half internships and an externship), and service opportunities (organizing events, mentoring, speaking, teaching, etc) that I would not have gone through had I not been a computer science major.
Typical college CS curriculums offer both programming-heavy and also theoretical classes, teaching students how to:
- view things logically and critically (I found myself to be a better problem-solver after a few CS classes, with things like jigsaw puzzles or Sudoku)
- consider edge cases others may overlook (this carries over into the real world.)
You also learn how to
- find and consider minute details
- plan, outline, design, and build large-scale projects and solutions to problems (What classes should you include? How about their attributes? Which language is best in this case? etc)
- persist and persevere (it’s important to think logically and keep a cool head when code doesn’t work how it should at first.)
- explain yourself (this is important — explaining design decisions, efficiencies, algorithms, variable names, and more.)
as well as some math, some technical writing and explaining, and more. Because of this, I’m also happy with who I’ve become as a CS student.
However, yes, it hasn’t been all compliments, rainbows, sunshine, and daisies. College CS forces you, by nature, to:
- get by on little sleep. Let’s make it a competition to see how little sleep you get the night before an assignment is due!
- be overly anxious and stressed (Yes, this is normal for most college students, but moreso in CS.) The competition for the “best” internships and jobs can be cutthroat pitting students who started sometime in college with ones who started when they were 14, 12, or even 7.
balance classes with interview prep. Yes, you learn algorithms and data structures in classes, but to pass a technical interview, you must put in even more hours practicing questions, interviews, or reading our bible, Cracking the Coding Interview.
sacrifice social lives, hobbies, and more to stay in and work. Yes, no one has the time, you have to make the time, yada yada, but I would love to not feel guilty watching Netflix or working out or doing something unrelated to tech. I would love to not say no to seeing a show or a game with friends because I have more reading or projects to do.
make it your life. You eat, breathe, and sleep tech. You spend so much time with tech people, you forget it’s normal to talk about music, art, sports, and more.
And yet…there’s a reason.
When I was a freshman contemplating declaring a CS major, I heard my department head tell another student something along the lines of: “There’s a reason CS majors are in-demand and get paid 6-figure salaries. It’s not easy. It is one of the most, if not the most, work-intensive majors there are. It’s not like math where the better you get, the fewer hours you put in. In CS, the best programmers spend the most time on projects.”
That’s really stuck with me, sort of like my high school senior quote: “Of course it’s hard. It’s supposed to be hard. If it wasn’t hard, everyone would do it. The hard is what makes it great.”
There’s a reason why college CS is a climb. There’s so much to learn in so little time. And yes, the curriculum doesn’t necessarily teach skills that translate directly to industry, but it does teach you how to think. Languages and frameworks may change, but being able to solve problems with code and algorithms will not. The CS skills we learn here will stick with us longer than if we solely did hackathons or online classes.
Yes, it is difficult and you have to make sacrifices, but nothing worth having comes easy.
Top comments (7)
Being an upper level student in a Computing Science major, This article definitely resonates with me. It's not easy and it demands a lot of time from you - but it's so worth it when you see all your hard work and knowledge come together.
The most important aspect was the mention of learning how to learn - as a CS, we're not taught all the languages and frameworks but instead we have the skillet to learn any of those. That's the easy part. The hard part is the software design/implementation which this article heavily talks on.
It's hard to tell myself to focus on a class that's about a language we tell ourselves we'll never use! And we might not. But the skills we learn while learning that language (or framework, or anything) will help down the line when we have to learn again.
I also feel very close to this studying computer engineering. I also see CS or CE hard as literally every year (sometimes every month) there are new technologies to learn about and used on the industry so we are like in a constant race!
YES! It's constantly changing and someone is always doing something to further themselves. There's no way to learn it all, even if we feel like we must.
Didn't do cs degree, find it hard to get the skills or get into anything in Australia without it. Never know with a bit more learning that will change :)