Ask HN: One thing you wish they teach in your undergraduate CS course?
After some 10 yrs in IT, I still dun see much value in my CS degree, why dun they just teach me these instead;
Step 1 - Find a(another) problem. Step 2 - Build an awesome product to solve the problem in Step 1. Step 3- Tag a price to your product. Now go back to step 1.
It make so much more sense.
(
10 comments
| 8 points
| on HN
)
Here's a shot at such a course that covers testing through RSpec and Cucumber: http://tinyurl.com/ucb-cs169
Name one good technical documentation you see recently? Not easy really, there's a few threads on HN on it. I guess that's why most used a wiki for their technical doc, so that anyone can just come in and help correct any error documentation.
Depending on the university you go to, CS != Software Engineering. You don't encounter, and may not be even aware, of concepts like code reviews, build systems, or version control. By participating in an internship you are forced to address these gaps in your knowledge.
That being said, I don't think I would take away a single CS course I took as an undergrad and replace it with a course on software engineering practices. There is just too much strictly CS knowledge that is necessary for an undergraduate to learn.
What I would argue is that CS programs give you the background knowledge required to pick up whatever is needed for a certain task. For many, that task is not entrepreneurship.
Would a Software Entrepreneurship degree be cool? Of course, but it doesn't negate the worth of another degree.