36 ms·
But CS pays, and engineering doesn’t. If you plan on getting a job, that engineering degree is worthless when you’re at a whiteboard and the interviewer is aski
by jl2718 8y ago
But CS pays, and engineering doesn’t. If you plan on getting a job, that engineering degree is worthless when you’re at a whiteboard and the interviewer is asking some canonical CS question requiring implementation of a data structure that you don’t know the name of. Also, engineering is hard, like, lifetime of accumulated knowledge hard. It’s true for CS as well, but there are so many kids running the show that it’ll never be expected of you. And that’s okay because CS problems are easy, at least the ones you’ll get paid to work on. Load a poorly-written web page faster, given infinite compute resources. A/B test the color of the button to get more clicks. Engineering problems are hard. Shoot down a nuclear missile going Mach 32. You’ll spend a thankless lifetime trying to learn enough about things like microwave phase shift jitter and electron transport dynamics in indium phosphide before you really understand how hard that is. Instead, just get a CS degree, and call yourself an engineer when you valiantly build the backend of the “Yo” app.
- protonimitate 8y ago>>If you plan on getting a job, that engineering degree is worthless when you’re at a whiteboard and the interviewer is asking some canonical CS question requiring implementation of a data structure that you don’t know the name of. What software engineering program doesn't cover DS/A? Furthermore every answer to those cookie cutter whiteboard questions can be found in CTCI, leetcode, or any other DS/A textbook. Lets not pretend that a CS degree is some magic pass to getting a job in the field.