4 ms·
What's lacking in CS Degrees nowadays (Part 1)
- sophacles 17y agoI find this to be sadly true. I work for a university, writing software for research groups. I only have a Bachelor's degree, and many of the people I work with are working toward's ph.d.s or already have them and are doing post-docs. What they don't have is practical programming knowledge. I spent 3 hours yesterday convincing a group of grad students that the just because the library we are working with claims to be standards compliant does not mean that it is. I even wrote code to demonstrate how the library was broken and the simple steps to work around it. The other group members refused to believe the real life results, because the documentation and some ph.d. (who wrote the docs) said otherwise. The worst part of this is: it is not even a core bit of the research, it should be simple to say: hey this 3rd party thing is broken, but when we do foo, we get the behavior we want. I firmly believe every CS degree should include a practical component such as internships, or a demonstration of skills by working on OSS or similar. This would not only help cement the theory, but also help with practical issues like making code maintainable. Most current curriculums use throwaway homework assignments, encouraging and reinforcing ugly code.
- Maro 17y agoI agree... instead of trying to make up projects, schools should just send students on internship gigs at the end of 3rd and 4th year.
- kschults 17y agoWaiting until the 3rd and 4th year makes even less sense. The sooner that schools can get their students out in the real world, doing real world projects, as the author described, the sooner they'll learn how to develop good code. Schools should be pushing students to get internships after their second, and even after their first year. I'm in an internship after my second year of school, and I have many times wished I'd had an internship last year as well. Even still, I've learned way more this summer than I did in the first two years of college combined.
- Eastbeast314 17y agoI had 6 internships under my belt by college graduation and they taught me a lot. However, by and large, I learned more about workplaces and teamwork than about difficult programming situations. Internships, in most of my experience, don't encourage really hard programming work. I got that with my CS degree. The theory classes were 7 out of the 15 classes I took, but the programming classes were just as intense. We did complex image recognition in groups in Java the first year, tons of Scheme and Oz to learn concepts, and then wrote a whole networking stack and basic Linux OS in C. The latter two projects were significantly harder than anything I've done at an internship and required teamwork and a great deal of self-teaching. It may be that my experience was abnormal (the school had a small but recognized CS dept), but I got the meat of my practical programming skills at school (ignoring independent work for the sake of focused discussion). Internships were certainly useful - but in my reflections I don't think they increased my programming power, if you will, all that much compared to school.
- amelim 17y agoHere is the link to Part 2 http://theshyam.com/2009/07/what-could-be-done-to-improve-cs-degrees-part-2/ http://theshyam.com/2009/07/what-could-be-done-to-improve-cs...
- CGamesPlay 17y agoI've been programming as a hobby for years, am now a junior in a CS program and am consistently disappointed by the level of difficulty in my classes at school. When we do have to program, the grading criteria is so loose that it's difficult to fail at all.
- tokenadult 17y agoWhere are you majoring in CS? What are the names of some of the classes you have taken in your program?
- aidenn0 17y agoI 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.
- alexgartrell 17y agoFor my Software Engineering class, we had to make a contribution to an open source project. Firefox is about as "legacy system" as you get without learning COBOL. I think the better question is why didn't this guy seek out the MULTIPLE opportunities to do "real" development (Open Source, _Good_ internships, etc? It's not as if we're all (College CS Majors) twiddling our thumbs and being useless all year long.
- paulgb 17y agoI have mixed feelings about this. It sounds like the author's needs are better suited to a degree in software engineering than computer science. A CS degree is not a degree in programming or software development, even though that's the path many people take.
- lallysingh 17y agoIndeed. The specific stuff you get at a code review depends completely on who else is on your team -- stuff that's great at one place is terrible at another. It's stuff you pick up from the specific software industry you join when you get out of school, web, embedded, desktop, whatever. The stuff you learn in school is useful for any of these, and is the same for all of them. Equally important, you can really tell who's been through those courses or not, independent of how well their code fits the normal maintainability or performance requirements. Higher-level concepts are just lost on them, or, if they've managed to pick some of it up informally, so intermangled with other conceptually-different topics that clear thinking and analysis is nearly impossible.
- mquander 17y agoI strongly disagree that universities should be trade schools whose objective is to prepare students for the "industry." Aren't there loftier goals in life?
- Xichekolas 17y agoI agree with you, but the reality is that most people go to college 'to get a good job'. So most people expect college to train them for that job, and most employers have come to expect people to hit the ground running. My grandfather started working as a draftsman for a pipeline company after the Korean War. He had nothing more than a high school diploma, and he said he took the job because "it paid $3 an hour and I liked to draw". He spent the first year being trained in a special facility the company had set up just for that purpose. What company does that nowdays? I'm sure there has to be some, but it's far from the norm.
- scott_s 17y agoI think the expectation for any engineer fresh out of school is that they will need some on-the-job training to learn how to be an engineer in practice.
- timwiseman 17y agoYes, but the key word is some. There is a major difference between expecting someone to grow through experience and giving them some initial guidance and training on that specific job and teaching someone everything they need to know in practice when they have some hazy idea of the background theory. This is particularly true in software. I do not know about other companies, but when I got my first "real programming job" I was given two weeks of on the job training. That focused on things like that particular company's code layout standard, naming conventions, an overview of the code base already written for the piece I would be working on, and some of the HR/administration requirements and procedures. I was expected to know how to program already.
- scott_s 17y ago
- nwjsmith 17y agoI'm a CS undergrad, and I'm working building software in the 'real world' for the summer. There's no way they could teach this kind of experience in the classroom or with projects. I like the idea of OSS work as a course requirement, but the only way to learn how to _really_ program is to _really program_.