What did you cover in your undergrad CS degree?
catalystclass.com
What did you cover in your undergrad CS degree?
1–10 of 57 posts
Re: What did you cover in your undergrad CS degree?
#2This doesn't look like a CS degree---this looks more like software engineering requirements. CS and SE focus on distinctly different things. I might suggest changing the page title.
Re: What did you cover in your undergrad CS degree?
#3This doesn't look like a CS degree---this looks more like software engineering requirements. CS and SE focus on distinctly different things. I might suggest changing the page title.
Many CS degrees are all there are at institutions. SE is merely a focus you can take in that.
Re: What did you cover in your undergrad CS degree?
#4I got to check three of these, but one (version control) was only because I took game programming. A person could easily earn a CS degree from my school without using version control for any class.
Re: What did you cover in your undergrad CS degree?
#5Personally I find things like version control and system administration to be things that students should learn for themselves. They should be encouraged, even actively encouraged (in fact they are already in most institutions) but there shouldn't be a class dedicated to this stuff. You are in University, studying CS ffs. If you can't learn such petty things for yourself, what good are you?
Re: What did you cover in your undergrad CS degree?
#6Personally I find things like version control and system administration to be things that students should learn for themselves. They should be encouraged, even actively encouraged (in fact they are already in most institutions) but there shouldn't be a class dedicated to this stuff. You are in University, studying CS ffs. If you can't learn such petty things for yourself, what good are you?
While I agree that a course on version control wouldn't make any sense, I'm pretty torn about this. Most of the developers I know have shitty git habits, and it's not an accident.
Re: What did you cover in your undergrad CS degree?
#7Personally I find things like version control and system administration to be things that students should learn for themselves. They should be encouraged, even actively encouraged (in fact they are already in most institutions) but there shouldn't be a class dedicated to this stuff. You are in University, studying CS ffs. If you can't learn such petty things for yourself, what good are you?
I left a lot of options blank that were in fact encouraged, and which professors would help us with if asked, but were not really part of the curriculum. For example, we were strongly encouraged to use version control for our group projects, especially in third and fourth year courses (like operating systems and theory of computation) and obviously estimating timelines is a necessity for any project (computer science or otherwise). Code testing is a big one I wish we would have learned or been encouraged to learn, since I'm still horrible at that, but I hear that same sentiment from nearly every programmer I've ever met, so I suspect a handful of college lectures wouldn't have helped much.
Re: What did you cover in your undergrad CS degree?
#8The table of results is hard to read. More contrast between the results bars and the background would help.
Re: What did you cover in your undergrad CS degree?
#9I graduated with a CS degree ten years ago and I could only check the following:
Designing data structures Analyzing algorithmic complexity (Big O)
Version control was glossed over in my class with little importance given to it.
Re: What did you cover in your undergrad CS degree?
#10Personally I find things like version control and system administration to be things that students should learn for themselves. They should be encouraged, even actively encouraged (in fact they are already in most institutions) but there shouldn't be a class dedicated to this stuff. You are in University, studying CS ffs. If you can't learn such petty things for yourself, what good are you?
While I agree that a course on version control wouldn't make any sense, I'm pretty torn about this. Most of the developers I know have shitty git habits, and it's not an accident.
I think the best approach is to integrate tasks like version control across many subjects.
For instance, many programming exercises in various subjects taught at my university give the students a basic framework with missing functions, or a test harness, or some other piece of code that needs to be finished. These could have been shared via a version control system, and delivery could be made that way as well (using pull requests, branches, or some other feature).
That way, students would be encouraged to use version control while working on the exercises.
The way it actually is done here, though, is basically "learn version control yourself and justify your choice of version control system in your report" when doing group projects.