6 ms·
How is any of that computer science? I mean, is there a list out there for astronomy students that includes, grind your own lenses?
by gaius 15y ago
How is any of that computer science?
I mean, is there a list out there for astronomy students that includes, grind your own lenses?
- zheng 15y agoIt 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
- jff 15y agoThis is Hacker News, sir--how dare you suggest that coding positions exist which are not web development? :)
- jarek 15y agoHaven't you heard? Mobile native applications are the new black. Great job security.
- xtreegold 15y agoIn fact there should be a buy an Arduino (http://arduino.cc http://arduino.cc) board and program it item on the list.
- parfe 15y agoWhat do you think graduating computer science majors go on to do?
- ghurlman 15y agoThat'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.
- gaius 15y agoI 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...
- brianbreslin 15y agoLAMP exposure gives the CS student useful experience.
- leftnode 15y agoChill, I think it was just an example he used.
- andos 15y agoQuestioning specific advice is part of the learning, I believe.
- GHFigs 15y agoSpecific 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."
- bluesnowmonkey 15y agoSure, 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".
- quanticle 15y agoIts 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.
- rmb177 15y agoI 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.
- endtime 15y agoWhile 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.
- pavel_lishin 15y agoSpecifically, 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?
- Apocryphon 15y agoBut being able to write a CRUD app is a basic task. Like writing a FizzBuzz program.
- Caerus 15y agoSpeaking 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.
- bdhe 15y agoThis 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.)
- tolmasky 15y agoYeah 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).
- pilgrim689 15y ago