These are the most presumptive headlines. Programmer encapsulates many disciplines just as a writer encapsulates those who write comics, novels, plays, ads, articles, law and speeches. Stop assuming everyone is a web developer. And don't deign to tell programmers what they should know.
+1. Expected a serious list, instead I saw stupid Ruby/JS/HTML garbage. And no, I do not need to know "100 Vim Commands" - because Visual Studio is "100" times better.
Here is the real list:
1) know one modern web tech;
2) know one OOP language;
3) know one functional language;
4) be familiar with one dynamic language;
5) remember where to look up theoretic bits like algorithms.
Hands up: who had heard of "docking" in the sense of http://x86.cs.duke.edu/~brd/Teaching/Bio/asmb/current/Papers...? For me, that didn't even come from the same ballpark. And that is after I accepted that CSS cheat sheets and type theory were in the same ballpark.
I don't know why "what every computer scientist should know about floating-point arithmetic" is not in here. Ruby or the last framework are just fads, but IEEE754 is here to stay and nobody know how to use it (and I never remember the details myself, I'm always struggling).
I like to tell IEEE754 as an improvised story, because it's so rich in history as far as data types go.
They were first introduced in 1941 on the German made Z3 compuer. Whic means, yup, we can blame nazis for 0.1+0.2 == 0.30000000000000004
In all seriousness, more programmers need to understand this. I've seen more than a few beginners go rant about how awesome their language X is when contrast against language Y because language Y has bugs like 0.1+0.2 ... then they're blown away when the see their language too has the same "bug".
Great resource, thanks. But oh man, typography, character sets, CSS3...you are going to have a lot of frustrated developers scrolling through this. :) Not many have a good handle on all three of those AND functional programming, and you know lots of people measure themselves against these lists...
Heh. But while it's silly to put too much into measuring yourself against arbitrary lists, reasonably good ones like this should at minimum be a guide to "Here be dragons". As in areas that are messy and/or otherwise complicated enough that you should make note so that you'll know to study them if needed in the future. Mixing metaphors while still staying reptilian, so that you don't one day ask yourself "Why have I found myself in an alligator infested swamp?"
The functional programming one is great. As a self-taught programmer who has mostly learned on the job, I've struggled with understanding functional programming (since I've never had the opportunity to use it for work), and that helped me along quite a bit.
Am I the only one who had to google the "docking problem"? I've been programming for over 30 years, and not once have I had to model the quaternary structure of complexes formed by two or more interacting biological macromolecules (http://en.wikipedia.org/wiki/Macromolecular_docking).
There are people (myself included) who cannot remember how exactly to use tar, the Unix command. For me it always goes like this: "Is it 'tar -fzhf... ' or 'tar -vgsf...'? Ok, I'll google it again, just this one time, promise".
[+] [-] uuilly|12 years ago|reply
[+] [-] ___Dev___|12 years ago|reply
Here is the real list:
1) know one modern web tech; 2) know one OOP language; 3) know one functional language; 4) be familiar with one dynamic language; 5) remember where to look up theoretic bits like algorithms.
[+] [-] maurits|12 years ago|reply
[1]: Favourite programming related academic papers
[2]: Influential books every programmer should read
[3]: Favourite (or most brilliant) Algorithms
[1]: http://stackoverflow.com/questions/358033/what-are-your-favo...
[2]: http://stackoverflow.com/questions/1711/what-is-the-single-m...
[3]: http://cstheory.stackexchange.com/questions/189/algorithms-f...
[+] [-] jakejake|12 years ago|reply
[+] [-] gtani|12 years ago|reply
this also, re fogus' blog
https://news.ycombinator.com/item?id=2979458
http://blog.fogus.me/2011/09/08/10-technical-papers-every-pr...
[+] [-] tel|12 years ago|reply
[+] [-] Someone|12 years ago|reply
[+] [-] nandemo|12 years ago|reply
[+] [-] nraynaud|12 years ago|reply
[+] [-] bdg|12 years ago|reply
They were first introduced in 1941 on the German made Z3 compuer. Whic means, yup, we can blame nazis for 0.1+0.2 == 0.30000000000000004
In all seriousness, more programmers need to understand this. I've seen more than a few beginners go rant about how awesome their language X is when contrast against language Y because language Y has bugs like 0.1+0.2 ... then they're blown away when the see their language too has the same "bug".
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] themodelplumber|12 years ago|reply
[+] [-] hga|12 years ago|reply
[+] [-] nawitus|12 years ago|reply
[+] [-] ___Dev___|12 years ago|reply
[+] [-] zmmmmm|12 years ago|reply
[+] [-] mynameisme|12 years ago|reply
[+] [-] sbarre|12 years ago|reply
A good collection overall..
[+] [-] joshvm|12 years ago|reply
http://projectmona.com/bits-of-brilliance-session-one/
http://projectmona.com/bits-of-brilliance-session-two/
http://projectmona.com/bits-of-brilliance-session-three/
http://projectmona.com/bits-of-brilliance-session-four/
[+] [-] rubiquity|12 years ago|reply
[+] [-] SkyMarshal|12 years ago|reply
https://www.hnsearch.com/search#request/all&q=papers+every+p...
[+] [-] inopinatus|12 years ago|reply
[+] [-] t1m|12 years ago|reply
[+] [-] gruseom|12 years ago|reply
http://library.readscheme.org/page1.html
[+] [-] cpdean|12 years ago|reply
[+] [-] marcelocamanho|12 years ago|reply
[+] [-] beggi|12 years ago|reply
[+] [-] anon_d|12 years ago|reply
[+] [-] paganel|12 years ago|reply
[+] [-] noiseapple|12 years ago|reply