Advice for Computer Science College Students
joelonsoftware.com
joelonsoftware.com
Good advice here. Get in the habit of WRITING (in a form that keeps an archive, that is email preferably over unarchived chat) to professors about any issue that comes up in class.
How bad of a problem? Well, quite potentially the worst kind: a serious buffer overflow problem that could result in a remote execution vulnerability. This is just the sort of thing that gets patched every Tuesday as engineers come to the "oh shit!" realization that yet another bit of crusty code using some ancient "clever" (actually lazy) idiom has been sitting around just waiting for some ne'er do well to take advantage of it and create yet another 400,000 system botnet.
It's good to have a solid knowledge of C programming fundamentals, but actually writing good, safe C code is non-trivial. Moreover, the mentality that one can just slap together some "efficient" C code and ship it out the door has resulted in more heartache and more sysiphean turd polishing than almost any other single software engineering mistake.
I'm just about to intern for a second year Electronic Arts. If you saw a resume with two consecutive internships at the same place (same position and team, too), would you think better or worse of it as compared to someone who did two different, fairly big-name companies?
Now, two different internships might give you completely different experiences, or depth as you return to the same project as before if you go back to the same place. But those things are both valuable in and of their own.
In short. Enjoy EA. Don't worry.
I thought his shot at Facebook in one of the opening paragraphs was funny- just in general it's interesting to see how so much has changed in just a few short years to where a leading blogger could be so wrong about what was to come (nothing again Joel).
I wonder what Caterina Fake would say about Joel's list (http://www.caterina.net/archive/001234.html), assuming the hackers he's speaking to are also entrepreneurs?
I hate it.
The homework two weeks ago? Prove that p = !!p. I gave up.
I don't get it, I'm afraid =\
If you get into languages, the language part of the proofs are important, but only insomuch as recognizing/identifying if something can be parsed with an X or Y or Z.