4 ms·
I used to think that CS programs need reform for this very reason. Now I've turned around completely. Colleges are optimized for getting broad ideas and theor
by aidenn0 17y ago
I used to think that CS programs need reform for this very reason. Now I've turned around completely.
Colleges are optimized for getting broad ideas and theories across. Theory of computation, algorithms, etc. are necessary for programming.
The point this article makes is that those ideas and theories are not sufficient for being a professional programmer. So what? Almost all engineering fields require some sort of on-the-job training. For software development, it's about writing maintainable code. I don't think this is something that can be taught easily in a CS program, and you'd have to stop teaching something else to do so (probably lots of something elses, since I don't see how you could do it in one semester).
Furthermore, either the majority, or a substantial minority of CS PhDs can't do this right, so it's strange to think that they will be able to teach this.
- fsniper 17y agoI think academia is not about business and should never be about business. IMHO If the academia starts to aim industry students will stop doing research, innovating or doing teaching. This will be catastrophic for CS and industry.
- timwiseman 17y agoIt sort of depends on how you define Academia. If by Academia you mean "Liberal Arts + Sciences" then I agree, but by that definition all major universities go far beyond that. Universities teach those, but they also have some programs focused on practical applications (and some people think of Academia as simply "what universities do"). The obvious example are the professional degrees such as the JD, MBA, MD, etc. Engineers and architects are also expected to emerge being able to put those skills to use almost immediately after graduation. They all come with some on the job training, but that is true of virtually every job/profession. Those with "applied degrees" are expected to have received the vast bulk of the training they need to enter and work in that industry at college and it would be catastrophic for industry if they did not. Now, CS as it (mostly) is now is an academic degree in the former sense. The question is whether "Software Engineering" should be separated out form CS as an applied degree similar to other forms of engineering. Personally, I think it should. This would free "Pure CS" to focus on theory and algorithms and the mathematics behind them and general research while providing employeers and those students primarily interested in becoming employed with a more focused degree that can include more methodology while deemphasizing the theory. There would of course be vast overlap between CS and Software Engineering, but this is just like chemical engineering and chemistry being separate. The overlap between the two is huge, but they are not identical and different people chose one of the two deliberately and with good reason.
- fsniper 17y agoSeparating CS and Software engineering is a must in this case. But thinking of Software engineering as a "applied degree" is downgrading what Software Engineering could be. Software Engineering can be a research and innovation degree. But nowadays it's not thought as one. There are just "programing degrees" specialized for these cases. (there are in Turkey. But I'm not sure about USA and Europe)
- timwiseman 17y agoBut thinking of Software engineering as a "applied degree" is downgrading what Software Engineering could be. It is largely a point of view, but I would respectfully disagree. I suspect most people would think of an MD as an "applied degree" (or applied doctorate as the case may be), but many MD's engage in research and innovation. The same is true of the engineering degrees.
- Xichekolas 17y agoWell really the issue is that the field needs to be split. I too once thought my CS undergrad was worthless because it was all this theory and no practice (at least not practice at inheriting bad code, improving it, and leaving good code to someone else). But really the problem was that I went into CS thinking I was going to get a degree in Software Engineering. They are in fact very different things, and should be different degrees in my opinion. Just like there is a different degree for Math and Accounting, or Architecture and Architectural Engineering, there is a pretty big gap between CS and Software Engineering. Of course they have things in common, and could share many introductory classes, but separating them would make it more clear up front what you are getting yourself into, and make it more clear at the end what you actually learned. That said, I'm glad that separation hadn't happened when I was an undergrad. I went into college thinking that I wanted to be a Software Engineer, and was fairly disappointed to 'waste all my time' on this theory stuff. But now, a few years after graduating, I find the theory much more engaging, and am going back to grad school for more of it. If I had had the option of a Software Engineering degree when I started, I might never have discovered the fun that is CS.
- scott_s 17y agoI agree, but I'm not sure if the field of Software Engineering is ready yet for us to split the degrees. For example, see the ACM's position from 2000 on licensing Software Engineers: http://www.cs.wm.edu/~coppit/csci690-spring2004/papers/selep_main.pdf http://www.cs.wm.edu/~coppit/csci690-spring2004/papers/selep...
- Xichekolas 17y agoProbably true. As others have pointed out, the best way to learn this stuff is to do it, hopefully with a mentor to speed you along. If you are going to learn that way, you might as well earn a paycheck at a company rather than paying tuition to a University. If you were setting up a Software Engineering degree, one good route might be to partner with some local company. They get cheap work, and the students get real world experience and access to mentors (senior people at the company) to rapidly improve their abilities. Courses would probably center around languages and classes of tools (Introduction to Source Control Management, Introduction to Automated Testing), and, like Architecture, lots and lots of studio time.