3 ms·
I strongly disagree on not needing to know the fundamentals. Can you get a job without them? Sure. Can you even create a successful product without them? No dou
by overgard 7y ago
I strongly disagree on not needing to know the fundamentals. Can you get a job without them? Sure. Can you even create a successful product without them? No doubt. Will your product take up 50GB of RAM, have un-debuggable hitches, erratic performance, and weird bugs when the 5000 dependencies you have change subtly on an update? YUP. Will you have a bunch of new developers that replace your old developers because of high turnover that want to rewrite it two years down the line, but don't realize they don't have the skills to do it better than the original people did? Probably!
- deleted 7y ago[deleted]
- TheRealPomax 7y agoAs a software engineer, I call elitist hyperbole bullshit on this. It's what I might expect from a retired computer scientist or software engineer that has hopelessly lost touch with the actual professional field, or someone who is far enough removed from the title to not know the difference between "programming" and "software engineering".
- sandofsky 7y agoAs a software engineer going on fifteen years, I roll my eyes at the claim of elitism. Over my career, I’ve witnessed tons of similar disasters caused by not grasping CS fundamentals. It isn’t elitist to expect a building architect to understand physics, a doctor to under biology, or a developer to grasp CS. It doesn’t need to be a barrier to entry, but it will likely be a career blocker down the line.