10000 things all CS students should do before graduating
151–160 of 164 posts
Re: 10000 things all CS students should do before graduating
#152I think a lot of people here missed the point. This isn't a list of "stuff that will make you SUPER BALLER," it's a list of easy things that teach you very much and give you a lot of confidence for a very small amount of effort. Plus, all of these tasks are highly relevant in our web database-driven world. Not everyone wants to be Johnny Writes His Own C Compiler Geek, but every CS student SHOULD be able to configure…
I'm surprised that most people seem to have ignored this line: > it’s about doing , as opposed to knowing or learning After graduating, I had to teach myself everything in that list before I could actually do anything that I found interesting. Now, this obviously doesn't apply if you're, as you say, writing a compiler, but for the average CS student, this is a great list to complete.
Re: 10000 things all CS students should do before graduating
#153Re: 10000 things all CS students should do before graduating
#154Earlier quoted context omitted.
Those sound like engineering problems, not science problems.
I have a bias towards the systems side of computer science. I didn't mean to neglect my theoretical brethren. Maybe we can both agree that the OP is off the mark.
Re: 10000 things all CS students should do before graduating
#155Re: 10000 things all CS students should do before graduating
#156I'm a computer scientist, not a web monkey (FOOTNOTE). I'd say these are not the things all CS students should do before graduating. The field has much more to it. How about: 1) add or modify a significant feature of a working kernel 2) write a toy programming language 3) program in a programming language with concurrent constructs (e.g., erlang) 4) study some theoretical area, develop a practical application based o…
Re: 10000 things all CS students should do before graduating
#157I'm a computer scientist, not a web monkey (FOOTNOTE). I'd say these are not the things all CS students should do before graduating. The field has much more to it. How about: 1) add or modify a significant feature of a working kernel 2) write a toy programming language 3) program in a programming language with concurrent constructs (e.g., erlang) 4) study some theoretical area, develop a practical application based o…
Most CS students worth a dime could write programs to do these things.
Re: 10000 things all CS students should do before graduating
#158I'm a computer scientist, not a web monkey (FOOTNOTE). I'd say these are not the things all CS students should do before graduating. The field has much more to it. How about: 1) add or modify a significant feature of a working kernel 2) write a toy programming language 3) program in a programming language with concurrent constructs (e.g., erlang) 4) study some theoretical area, develop a practical application based o…
Stuff on the list gets you jobs. Your stuff doesn't.
Re: 10000 things all CS students should do before graduating
#159Earlier quoted context omitted.
I wouldn't recommend that EVERY CS student do those. I mean, I would, but you can't expect every person to be able and willing to build any of those things. I think that this list is great in that it's reasonable; none of these things are particulalry hard, but each one of them actually sounds fun and produces something cool.
I assume he means putting together a computer in the sense of constructing one from commodity parts, in which case that one is definitely in line with the rest of the list. The other two are certainly more advanced exercises than the rest, but I think they are absolutely things CS students should be expected to be able to do, though many won't be willing to. Many won't be willing to do the other things on the list ei…
Re: 10000 things all CS students should do before graduating
#160How is any of that computer science ? I mean, is there a list out there for astronomy students that includes, grind your own lenses?
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