Hacker News Reader

It just means you've been doing jobs where CS is (apparently) unimportant. If you're ok with that type of job then by all means, continue, it pays the bills. The downside is that it might get mind-numbingly boring in the future. Pushing bits between API calls isn't exactly computer science.

View on HN

CS is unimportant in 99% of jobs. What's important in a job is making an impact in the company you work for. This means building product features, improving systems etc. but this rarely intersects with "CS" problems

People think CS is unimportant, which is why we have crap software left, right and centre. But I don't want to get into that, so let's suppose you're right. What OP needs to figure out is if a job where CS is considered unimportant is what they want from their professional life. Pushing bits between API calls and learning new frameworks, building product features into a codebase without breaking existing ones.

You mean CS is unimportant for 99% of all code monkeys. But it is absolutely necessary for bleeding edge development and creating libraries that people who deem CS unimportant. It’s like saying that math is a complete waste of time because no programmer needs more than school algebra ever. True? Absolutely! Do we still need math? If you married rich or grew up rich then it’s a nice brain teaser. Otherwise touch grass.

Reply on news.ycombinator.com