|
|
|
|
|
by rpedela
4572 days ago
|
|
For #3, I am starting to think we should split off a portion of computer science and call it software engineering. People who are interested in the theory of algorithms, etc can do computer science. Those that want to learn how to build fault-tolerant, scalable systems can do that in software engineering. It is similar to how chemistry and chemical engineering are split. Of course you still need to get a basic understanding of how computers work with a software engineering degree, but knowing how to mathematical prove some algorithm is O(log n) is pretty pointless for most (not all) jobs in industry. One of the things that is not taught well across the board in computer science programs is how to actually write code that is readable and maintainable and how to work with a team using source control, bug trackers, etc. Just to be clear, I am sure there are programs that do this well, but based on my experience they are not the norm. |
|
I agree, but IMHO most jobs in the industry that don't require you to prove that an algorithm is O(log n) shouldn't need a degree at all.
In the area of the world where I live, if you want to be an electrician, you can do that after you finish high school. You have to take a course and get a certificate for it as a legal requirement (which is true of any profession where you can get people killed) but it's pretty straightforward, and the course only involves pretty basic stuff.
And don't look down on electricians. My degree is in EE and when I need some work done on the installation in my house, I call an electrician. I could do what they do, but sloppily and with far more dangerous results.