/prog/ 2012 challenge

Brothers and sisters,

As the end of the year comes closer, and we reflect on what has happened on /prog/ this last year, we have to admit that we did not accomplish very much. Perhaps in our private lives, yes, but here on /prog/ we have spent the majority of the year trolling, meta-trolling, complaining about it and going nowhere in particular. If we look at our community I'm going to say we have very little to be proud of: /prog/ kinda sucks.

I say we change all that. I say in 2012 we band together and prove that /prog/ is better than it has ever been before just by making it so. That we can come to /prog/ with an expectation of lulz and wisdom. I'm willing to make the effort, who's with me?

ITT post your new years resolutions for /prog/, I'll start:

* If I have nothing substantial to say I will sage it.

>>67
But... SICP already exists.
SICP has its scope: being an introductory CS book. I was thinking of something more general and in-depth, ranging from lambda calculus and type theory to CPU design and DEPLOYING SUCCESSFUL ENTERPRISE JAVA APPLICATIONS (just kidding on the last one)
But seriously, have you looked at this shit? http://wla.berkeley.edu/~cs61a/fa11/lectures/functions.html
Wait, that's FIOCP? It's worse than I thought. I mean, introducing assignment in the second example of the fourth subsection of the first section of the first chapter? They've already got SICP wrong.