5 ms·
CS != software engineering, too. Like your chemistry example. There's chemistry, and then there's chemical engineering. Chemists worry about the properties o
by AnimalMuppet 7y ago
CS != software engineering, too.
Like your chemistry example. There's chemistry, and then there's chemical engineering. Chemists worry about the properties of atoms and molecules, and reactions that move from one state to another, and about the energy differences in reactions. Chemical engineers worry about how to efficiently make the stuff in multi-ton quantities without blowing up the city. It's related, but it's really a different set of concerns.
In the same way, CS worries about the efficiency of algorithms, and about what things particular language features make easier or harder to express. Software engineering worries about how to efficiently construct and maintain larger programs that adequately do what is needed. [1][2]
The thing is, almost everyone who graduates with a CS degree is going to be employed as a software engineer, not as a computer scientist. I fear that their education is mostly preparing them for the wrong thing.
-----
[1] Or perhaps, "construct less inefficiently" - there's inefficiency no matter how well you do it, but you have to control the amount of that, or it will destroy you.
[2] Note that I said that they "adequately do what is needed", rather than bug-free. Larger programs are never bug free.[3]
[3] Well, almost never. You can get there with formal verification, if you have a bug-free specification, and if the formal verification covers every relevant category of bug. But that's really difficult to do, and we're back at the "less inefficiently" issue.
- M5x7wI3CmbEem10 7y agowhat should software engineers focus on learning then? should they avoid typical subjects such as operating systems & compilers? src: http://teachyourselfcs.com http://teachyourselfcs.com
- peter_d_sherman 7y agoWhat do you believe that you do not know? Focus on learning that thing first; it will lead to other areas of things you don't know, which will lead to others... Socrates said it best, "The true knowledge consists of knowing that one knows nothing". But that being said, there are a ton of interesting areas with respect to computers and programming. Pick one or pick several, keep an open mind, try to learn from whatever source you can (Books, classes, articles on the web, self-experimentation, etc.). It doesn't matter where you start... just start! <g> Also, if one book/class/teacher/article is too difficult -- find a simpler one, or one that simplifies the topic, and learn from that one first! Then, Lather, Rinse, Repeat, and eventually you'll have 12 PhD.'s, like most normal people who are computer/programming enthusiasts(!), ...or you'll become a reclusive crackpot like myself! <g> (Shakespeare: "Much learning doth make thee mad!"... well, that's what happened to me! <g>) Anyway, wishing you well in your quest!
- OJFord 7y agoWell.. some software engineers are writing OSs & compilers, it's not like you hire a scientist for that and an engineer for anything else. IMO CS is the right core thing to learn; software tooling & frameworks are easily picked up interning, in on the job training, and are more professional development than core knowledge. If you compared an education in building a state of the art webapp vs. CS theory today, in.. idk, even just ten years, the webapp tech would be obsolete and the CS theory would likely be as solid a grounding then as it was twenty years prior.
- peter_d_sherman 7y agoAbsolutely correct, CS != Software Engineering. CS != Code, as a previous poster suggested. CS != Business aspects of software development. CS != Guarantee that you'll get a job you'll like as a programmer, or even a job as a programmer. CS != Guarantee that you will be able to fix systemic problems in systems, understanding, culture or process in corporations or other organizations, by fixing code. CS != Guarantee that you'll launch a successful website, or start a successful startup. CS != Guarantee that you'll be able to raise venture capital, or be able to sell enough to gain your first customers to become "ramen profitable". CS != Guarantee of success, or that you'll get what you want in life... I am 99.44% self-taught -- my opinion is that CS degrees are overvalued and overpriced, but that being said, they're not wrong for everybody...
- DeathArrow 7y agoOn the contrary. I feel that having a formal CS education (VS and MsC) in CS, made me a much better software engineer and a better coder. Most of the stuff I use (languages, tools, frameworks) I've learned myself. But CS courses have taught me a lot, I have a deeper understanding of how things work and I can solve hard problems, I know instinctively where to look to solve an issue, and what I need to research to make things work as they should. Based on my experience, employers tend to prefer people with CS education over people without, if that is the only difference. Also, talking with my peers, I have the sense that people with formal CS education managed to negotiate better salaries. Also, I my country, programmers with degrees in CS have lower income taxes. For me it payed big time to spend that time learning, even if in the first two years when the courses seemed boring I did have the opinion that I was wasting time. Some of my colleagues dropped out to work in the industry, some were working and studying in parallel. Those who dropped out have a harder time now. They have a harder time finding a good workplace and they have lower wages. Would you agree to undergo surgery by a self taught physician or you would trust more one with formal education?
- peter_d_sherman 7y agoDid I not say "they're not wrong for everybody", in what I wrote? ? Look, more power to you if you have a CS degree. Sure, they can open doors, I agree. If I were an employer, and I had only two job applicants to choose from, and the choice was between someone with a CS degree and without one, and there were no other differences, nothing different in the way that they thought, no difference in what books they read, no difference in their general level of intellectual achievement, no difference in their goals and aspirations (perhaps one strongly desires to learn technical things without having a degree, and perhaps one does not...). Well, without any of those other differences, if one has a degree and the other doesn't, then yes, I'd choose the one that has the degree over the one that doesn't. But that's assuming that I'm a standard employer... and that I don't know the first thing about CS myself... If I'm a smart employer, I might test both individuals' ability to cognitively reason about problems. For example, I might have both candidates add the numbers from 1 to 100, and see what they do. This was a challenge that was historically put forth to Carl Friedrich Gauss when he was a student (I should point out, he didn't know the first thing about computers or programming, as they didn't have computers, programming, or CS degrees back then). All of the other children attempted to add the numbers from 1 to 100 one at a time, for example, 1+2 (3), 3+3 (6), 6+4 (10), etc. This took them a very long time. You see, the teacher had expected that this would take a long time for most students, that it would keep them occupied. That was the teacher's goal. The teacher was very surprised when after a few minutes when Carl Friedrich Gauss' hand shot up. He had solved it! He had solved it not by adding all of the numbers one at a time, but solved it by realizing that if you added the first term and the last term (1+100, 2+99, etc.), it resulted in 101 every time, now all you needed to do was multiply 101 by half of 100, which is 50. Which is much, much faster! We call that an algorithm. A CS degree is < 10% code, and > 90% algorithms. You see, the teacher could have used that simple test to see that Carl Friedrich Gauss -- was going to go places in life. He was going to go to great places, and do great things... and he did! Even without a CS degree... which they didn't have back then... If I gave this test, or others like it, other tests involving mathematical / logical reasoning to people with CS degrees and without, and if the people without a CS degree answered these questions correctly, reasoned correctly, it would show that they have the talent, they have the capacity for computer science, with a CS degree -- or without... "Would you agree to undergo surgery by a self taught physician or you would trust more one with formal education?" It will always be the person that persuades me that their knowledge/experience relative to the goal I'm seeking is the highest among all candidates. If that's someone university educated, then that's someone university educated. But show me a faster/better way to do things, and prove to me that you're knowledgeable and it works, and I'm all in...
- mettamage 7y agoI have the hunch that software engineering is easier to learn than computer science though (when you studied CS first). Struggling with your nth segfault and having no clue where it comes from teaches a person a lot of grit to stick with a problem. When software engineering comes along, the person who learned computer science has matured into how to stick tough situations out. The extra practice in being detail oriented doesn't hurt either. In that sense I feel like learning CS is getting a huge IQ boost into everything that is related to CS. But I'm still relatively new to software engineering. So far, picking up about SOLID, design patterns, testing patterns, and what not feels a lot easier than writing a compiler or writing an operating system or performing attacks like Meltdown/Spectre/<insert any research from VUSec>. Don't get me wrong: I should still respect it and work hard, but when I wrote a compiler I didn't even believe I was smart enough to build one from start to finish. I've had this multiple times over my CS student career. Now that I graduated, I still can feel like that but I have experienced it so many times, I simply know it's false. Now I know that I just need to put in hard work, and I'll be guaranteed to understand it. Are there more optimal ways to learn software engineering? Yes. However, the value of CS in relation to software engineering stands: learning software engineering is now easier. Moreover, universities usually don't teach more optimal ways and we're stuck with the toxic narrative that university sets us up for life.
- danielscrubs 7y agoCS is tricky the way doing integrals is tricky, programming is tricky the way driving on ice is tricky.
- mettamage 7y agoBut creating HOC React components is relatively easy to understand, provided you focus, if you have a background in CS. It's also relatively easy to understand if you've been programming for a while (I suppose).
- danielscrubs 7y agoWhen you put it that way, programming is not very tricky at all. ;)
- danielscrubs 7y agoThey are preparing us for the wrong thing indeed, but boy is it nice to have some knowledge that will stand the test of time. If I could go back I'd remove all the courses that aged like milk and left would only be theoretical CS.