News for hackers. Stuff that matters.
Re:10000 things all CS students should do before graduating by gaius on Friday June 24, 2011 @11:28AM (#2692545)
How is any of that computer science?

I mean, is there a list out there for astronomy students that includes, grind your own lenses?

Re:10000 things all CS students should do before graduating by Caerus on Friday June 24, 2011 @12:06PM (#2692701)
Speaking as a mechanical engineer, experience in fields related to your own, however tangentially, is extremely valuable.

Two example from my career:

I spent two summers working construction on job sites. Running pipe, cutting beams, and building scaffolding are skills I likely will never use again professionally. However, it gave me insight into what people who are directly affected by my work experience. I am now extremely careful to consider what the end users experience. Maybe moving the bolt holes from position X to Y will add 4 hours to my workload, but it will save the installer 30 minutes on every one they put in.

I started in computer engineering. I didn't go very far but thanks to those 2 semesters, my programming skills are miles ahead of many of my peers (although they are still quite primitive). This gives me the ability to write scripts/programs to create functionality that is nonexistant it my field. Sometimes it allows me to work projects that would otherwise be impossible, sometimes it just saves myself or others hours or even days.

I hope this doesn't come across as boastful, my skillset is woefully inadequate in many areas which my peers do have experience.

Neither of those skills were touched on in my engineering curriculum, but learning them made me a much better engineer. I would imagine many of these items, while not "core computer science", would make a CS grad better and more marketable.

Re:10000 things all CS students should do before graduating by quanticle on Friday June 24, 2011 @12:05PM (#2692699)
Its not, and that's the point. I've seen computer science students struggle at basic system administration tasks - even things like moving files and directories. I maintain that half the trouble we have deployment is that developers don't know anything about how configuration and setup works in the real world. This list helps to bridge some of that divide by having programmers deploy software, not just build it.

EDIT: I also think astronomy students should grind their own lenses and mirrors, so that they can understand the practical difficulties of building and operating a telescope.

Re:10000 things all CS students should do before graduating by endtime on Friday June 24, 2011 @12:40PM (#2692866)
While I'm surprised someone got through four years of CS without learning to use mv, if you are looking for 'developers' then you should look for software engineering majors, and if you are looking for sysadmins then you should look at people with two year associates degrees in information systems or something. CS is a branch of mathematics; expecting fresh CS grads to make good sysadmins is like expecting comparative literature majors to win spelling bees. They might do better than average but it's not really what they're educated in.
Re:10000 things all CS students should do before graduating by dsr_ on Friday June 24, 2011 @01:01PM (#2692946)
We don't have good programs in systems administration and network engineering, but we should. (Any major university starting one?)

In the meantime, a good CS program is a perfectly reasonable foundation for a career in systems and networks. I ran through the gamut of logic, basic logic circuits, assembly, algorithms, data structures, complexity and then features of various languages, operating system structures, and finally graphs, automata, networks and projects in all of the above. All of that is a solid base. As with anything else worth doing, you then need to build on that base with the tools of the day.

I suspect the overall high failure rate of IT projects is attributable to "people with two year associates degrees in information systems or something". I'd rather hire an autodidact with a degree in math, physics or engineering.

Re:10000 things all CS students should do before graduating by lsc on Friday June 24, 2011 @06:28PM (#2694192)
>I suspect the overall high failure rate of IT projects is attributable to "people with two year associates degrees in information systems or something". I'd rather hire an autodidact with a degree in math, physics or engineering.

yawn yeah, yeah, I know that going to yale makes you better than I am.

Kids today. No respect for the trades.

Everyone choosing a major out of highschool is encouraged to go in to something highly theoretical or impractical. I think it's a show of wealth. I mean, if you get a degree in fine arts or something, well, you had better have a rich uncle or something, right?

Granted, the fact that every SysAdmin education program I've seen was decidedly second rate doesn't help. /good/ sysadmin education programs would help a lot. Really, there is no excuse for the lack of good SysAdmin programs. *NIX is older than I am. It's not like the field changes faster than anything else to do with computers.

I think you have similar problems educating people as computer scientists and then expecting them to work as software engineers. We need a lot more software engineers than we need computer scientists; and if I need a program written, sure, I'd prefer an excellent software engineer who was also a computer scientist, but if I had to make the choice, I'd choose a software engineer who was not a computer scientist over a computer scientist who was not a software engineer for 95% of all projects. But what kind of high school kid choosing a major would choose to be a lowly Engineer instead of a Scientist?

Re:10000 things all CS students should do before graduating by jarek on Friday June 24, 2011 @01:05PM (#2692956)
If there's ever a program that should fall under a polytechnic or college umbrella rather than the university umbrella, systems administration and network maintenance is one.
Re:10000 things all CS students should do before graduating by Apocryphon on Friday June 24, 2011 @01:42PM (#2693094)
We're always going to have this issue, because IT and sysadmin will always be scoffed as something for vocational schools, dismissed by "real universities of pure knowledge and research." Major universities will never condescend to offer such programs.

And perhaps they shouldn't. But at the same time, vocational schools are still seen as having less prestige (and, thus leading to careers making less money) in the U.S. It's just an endless dilemma.

Re:10000 things all CS students should do before graduating by jleader on Saturday June 25, 2011 @12:52AM (#2694957)
"vocational schools are still seen as having less prestige..."

Except for a few vocations that have managed to get themselves tagged as "professions". There are a number of fields where students are supposedly taught to think in general-purpose undergraduate programs, and then taught the minutia of their chosen field in "professional school". e.g. law school, medical school, and a growing list of professional doctoral programs in fields like Psychology, Occupational Therapy, Pharmacy, Optometry, Nursing, Education, etc.

Maybe someday we'll have a "Doctor of Network Configuration" or a "Doctor of Database Schema Design"? (I'm not sure if I'm kidding or not)

Re:10000 things all CS students should do before graduating by Apocryphon on Saturday June 25, 2011 @03:06AM (#2695147)
Why shouldn't sysadmin or network engineering be turned into some sort of engineering major? What makes EE or Computer Engineering more deserving of the ivory tower than them?
Re:10000 things all CS students should do before graduating by Locke1689 on Friday June 24, 2011 @12:51PM (#2692912)
Google expects its software engineers to do all that and more with a computer science degree. So what if it's not taught in the major? You're smart -- figure it out.
Re:10000 things all CS students should do before graduating by endtime on Friday June 24, 2011 @09:41PM (#2694661)
Don't get me wrong, I'm plenty capable with real world stuff. I just don't like it when people think a CS education should mean learning Java libraries and design patterns and server configuration. I'm glad I wasn't forced to waste my time taking classes devoid of conceptual material.
Re:10000 things all CS students should do before graduating by ciupicri on Friday June 24, 2011 @10:39PM (#2694765)
I agree that CS shouldn't mean learning Java or ASP.NET from top to bottom, but it wouldn't hurt to have an idea about them. Also let's not forget that even Peter Norvig said Remember that there is a "computer" in "computer science".
Re:10000 things all CS students should do before graduating by brettnak on Friday June 24, 2011 @01:02PM (#2692949)
I'd go so far as to say that I've never read a job description that was looking for a CS major and didn't expect them to know how to do these things.
Re:10000 things all CS students should do before graduating by quanticle on Friday June 24, 2011 @03:51PM (#2693629)
This isn't "expecting comparative literature majors to win spelling bees." This is, "expecting comparative literature majors to be able to spell."

I don't think that programmers should be sysadmins. There's room in the organization for both roles. However, I do think that programmers need to understand the practical difficulties in deploying and maintaining a running application. The more difficult it is to deploy an application, the greater the chances of someone screwing it up. By putting some forethought into how their application code is organized and by making some small investments in automation up-front, programmers can save endless headaches for themselves and the sysadmins supporting them when it comes time to go live.

Re:10000 things all CS students should do before graduating by yesimahuman on Friday June 24, 2011 @12:57PM (#2692934)
Knowing how modern operating systems work is crucial to the study of many CS topics. At the end of the day, a CS major must understand the workings of all systems (because they can often be generalized). Hands-on experience is one of the best ways to achieve that clarity.
Re:10000 things all CS students should do before graduating by rmb177 on Friday June 24, 2011 @12:26PM (#2692801)
I agree, and count me as one of those who needs to learn sys admin tasks (though I can move files and directories around :) ). I developed a side project last year and used Google App Engine precisely because I've never setup my own web server. In the short-term I think it was the right decision as I had a tight deadline to get the app running. In the long-term I'm not so sure since I'm now locked into GAE.

So 0001 is definitely on my someday TODO list.

Re:10000 things all CS students should do before graduating by ghurlman on Friday June 24, 2011 @11:41AM (#2692597)
That's the point. There's a general disconnect in a good amount of CS programs between the curriculum and reality. This post is trying to bridge the two.

I'd also like to add:

  10000 Learn to use source control, use it to store your new LAMP code on Github.
  10001 Start studying design: web, graphic, type.
Re:10000 things all CS students should do before graduating by gaius on Friday June 24, 2011 @12:01PM (#2692680)
I am wary of that sort of very specific advice. Why LAMP, just because it's fashionable? There are many, many other sorts of web stack alone, let alone the many, many other sorts of application. Same with GitHub (which I use myself, btw), there are plenty of others.

It just sounds like ESR's advice, to be a great hacker you should be just like me...

Re:10000 things all CS students should do before graduating by bluesnowmonkey on Friday June 24, 2011 @01:49PM (#2693134)
Sure, just because it's fashionable. X86 is fashionable, C++, Java, JavaScript, HTML, CSS. You definitely should try to become familiar with everything fashionable in our industry. Yeah they're all messy, but they are the reality of how things are done. People who think they don't need to are why we have the term "ivory tower".
Re:10000 things all CS students should do before graduating by andos on Friday June 24, 2011 @12:56PM (#2692929)
Questioning specific advice is part of the learning, I believe.
Re:10000 things all CS students should do before graduating by GHFigs on Friday June 24, 2011 @01:28PM (#2693033)
Specific advice is good when the audience doesn't necessarily know enough about what they need to differentiate between the various options. Thousands of man-hours are wasted every day by people trying to decide which of two (or more) entirely adequate tools they should use.

I think it's better presented as a heuristic instead of an imperative (as it is here), though: "Use X until you can articulate a reason not to."

Re:10000 things all CS students should do before graduating by brianbreslin on Friday June 24, 2011 @12:03PM (#2692688)
LAMP exposure gives the CS student useful experience.
Re:10000 things all CS students should do before graduating by leftnode on Friday June 24, 2011 @12:04PM (#2692696)
Chill, I think it was just an example he used.
Re:10000 things all CS students should do before graduating by dpark on Friday June 24, 2011 @01:54PM (#2693152)
> 10000 Learn to use source control

This is much better advice than telling someone to install LAMP.

Re:10000 things all CS students should do before graduating by pavel_lishin on Friday June 24, 2011 @12:06PM (#2692704)

    10010 Work with at least one other person on a software project; bonus points if they are remote.
Re:10000 things all CS students should do before graduating by peregrine on Friday June 24, 2011 @12:19PM (#2692765)
Whats a good place to start studying for 10001? Say for someone engineering minded.
Re:10000 things all CS students should do before graduating by andos on Friday June 24, 2011 @01:16PM (#2692977)
I offer you a few gateway drugs:

— The Visual Display of Quantitative Information by E. R. Tufte;

— The Elements of Typographic Design by R. Bringhurst;

— The Design of Everyday Things by D. Norman;

— Don't Make Me Think! by S. Krug.

Beware of Tufte. Using charts to abduct engineers into the world of design is just dirty.

Re:10000 things all CS students should do before graduating by pavel_lishin on Friday June 24, 2011 @12:05PM (#2692700)
Specifically, grinding lenses for one specific type of telescope designed for looking at once specific thing.

Has everyone forgotten that there's more to computer science than writing a CRUD app with a web interface?

Re:10000 things all CS students should do before graduating by Apocryphon on Friday June 24, 2011 @01:47PM (#2693124)
But being able to write a CRUD app is a basic task. Like writing a FizzBuzz program.
Re:10000 things all CS students should do before graduating by zheng on Friday June 24, 2011 @11:37AM (#2692580)
It isn't computer science per se, but it is a list of common tasks that many CS grads will end up doing in their career. However, I think it is basically a list of things for those who are going into web/software dev type positions. If I've just been hired to write Roomba firmware, some of that might not be quite as helpful.

EDIT: Also, the list is numbered in binary

Re:10000 things all CS students should do before graduating by jff on Friday June 24, 2011 @01:42PM (#2693093)
This is Hacker News, sir--how dare you suggest that coding positions exist which are not web development? :)
Re:10000 things all CS students should do before graduating by jarek on Friday June 24, 2011 @02:04PM (#2693195)
Haven't you heard? Mobile native applications are the new black. Great job security.
Re:10000 things all CS students should do before graduating by xtreegold on Saturday June 25, 2011 @02:45PM (#2696249)
In fact there should be a buy an Arduino (http://arduino.cc) board and program it item on the list.
Re:10000 things all CS students should do before graduating by bdhe on Friday June 24, 2011 @12:23PM (#2692784)
This article has got me really conflicted. On one hand, I am a CS graduate, but on the other hand, I work in theory, and I would always point out to people that computer science and computer engineering are two completely different things. Unfortunately the two are often conflated in almsot all CS curricula. Maybe there ought to be two different majors, one that focuses on building systems and implementing algorithms (as suggested) and the second that focuses on the basic stuff, designing algorithms, working on math applied to computer science (crypto, AI, etc.)
Re:10000 things all CS students should do before graduating by tolmasky on Friday June 24, 2011 @12:39PM (#2692862)
Yeah in my experience (both personal and from interviewing people), you end up getting a poor introduction to both (at least at the undergraduate level) since in many universities the major can't decide which it wants to be. You have cases where people know of NP (but have never done a reduction), and simultaneously know of version control (but have never actually used svn or git). This is really unfortunate because I feel similar majors (like math and EE) probably prepare you better for these fields (math perhaps being a better precursor to real CS and EE giving you great fundamentals for programming/comp engineering). It seems more and more like there needs to be a clearer separation, something like how econ or finance is separate from math, where math majors don't really have to learn excel or financial formulas, and econ/finance majors don't have to learn linear algebra, and both can go pretty deeply into the things they actually care about.

The counter argument to this is that we often see computer engineers that lack a basic grasp of the importance of algorithmic complexity and theoretical folks who write terrible code. You have only to read some discussions on "JS performance" to see the ridiculous attention paid to making sure variables are local, when in almost all cases user programs are actually being slowed down by O(n^2) algorithms being used. Similarly, a lot of theoretical work takes a long time to make it into the "real world" because they are inaccessible to engineers (being written completely "in math"), and often when they do provide actual sample code for their work its written in a very sloppy way (from a "code organization" standpoint). It really would be ideal if you could have a major that covered both of these really well (and I'm sure there exist some that do, I obviously have not gone through every CS/CECS/EECS major in every university).

Re:10000 things all CS students should do before graduating by pilgrim689 on Friday June 24, 2011 @12:42PM (#2692871)
At University of Waterloo we make that distinction by having a Software Engineering program that's part of both the Math department (the department CS belongs to) and the Engineering department.

We also have Computer Engineering, which is a middle ground between Electrical Engineering and SoftEng. :)

Re:10000 things all CS students should do before graduating by parfe on Friday June 24, 2011 @11:41AM (#2692595)
What do you think graduating computer science majors go on to do?
Re:10000 things all CS students should do before graduating by gaius on Friday June 24, 2011 @12:01PM (#2692684)
That graduating computer scientists often get work as programmers is orthogonal.
Re:10000 things all CS students should do before graduating by metellus on Friday June 24, 2011 @12:23PM (#2692780)
...unless you read the title with an implied [to prepare for their job] rather than an implied [to be better at computer science].