kurumo

That should do as far as Tor goes, but the more general problem of explaining why is such a thing needed by your mom is much harder. (Unless she lives in North Korea or some such place).

My question about speed referred to syntactic parsing specifically. I am sure you can do entropy scoring faster than 200ms per sentence, but unless you have access to parses you are unlikely to be able to do more than purely extractive summarization. That's what Summly does, and every other summarizer on the planet as well. (Except perhaps Columbia's Newsblaster, but that's a bit of a different story).

Two players play a game with a single six-sided die. The player that starts can only win by rolling a 1. If he or she doesn't win, the other player gets to roll; he or she can only win by rolling a 6. The game continues until one player wins. What's the probability the first player wins (eventually)?

Bloomberg is hiring, Intern, H1B candidates are welcome.

http://careers.bloomberg.com/hire/internsearch.html

http://careers.bloomberg.com/hire/experiencesearch.html

C++, Java, .NET developer positions are available, as well as network engineers, UI designers, sysadmins, etc. Lots of real time and low latency infrastructure work, generally financial domain.

News R&D is looking for people to work on a real time news search engine. Great place to work on interesting problems.

http://careers.bloomberg.com/hire/jobs/job27500.html http://careers.bloomberg.com/hire/jobs/job27499.html

Also,

http://careers.bloomberg.com/hire/experiencesearch.html

Schrödinger's Cat trilogy especially

A few people said something to the effect "the real world is missing". It's true. Majority of CS programs appear to be years out of date with respect to the industry practice, whatever "the industry" happens to mean for you personally. To some extent this is inevitable, though we could be doing a lot more to address the issue - say, as someone suggested, via a separate course, one that is updated biannually. A course like this could and should include a discussion of things like source control tools, build tools, etc. Things like resource management idioms in languages of the day should be discussed explicitly: too often graduates of CS programs assume infinite resources or automagical cleanup, especially if they come from a background in languages that are garbage collected. A course in parallel programming presented via different languages and their approaches to parallelism would be fantastically useful; I would pay money to see it on OCW or similar.

Somewhat related to Dijkstra's complaint is the following concern: people are terribly bad at thinking about complexity, at all levels - from a single source file to a system composed of hundreds of separate processes. We would do well to discuss managing complexity explicitly in CS curriculum: to make people think about difficulty of maintenance, changes to a working system, rollout procedures for uptime, etc. A seminar on the subject of complexity management, from small to large scale, with examples, would be very useful.

Incidentally, this is something I have been thinking a lot about over the last two years, in part due to conducting a metric shitload of interviews for intro positions. There are things that my CS program was missing, and things that a majority of programs out there seem to be missing; understandably, what I can say mostly applies to the former.

http://www.wikipedia.org

http://ocw.mit.edu