p3ll0n

Are the data that will be used in the rankings losing their analytical validity since they will be from the 2005-2006 academic year?

Why wasn't the NRC able to produce its rankings more quickly, using more up-to-date information?

How many faculty members have switched institutions and departments since the NRC first started collecting data in fall 2006? This is very important because faculty data are a key part of the NRC's analysis.

1. Comparing local and remote files

$ ssh user@123.4.5.6 "cat /tmp/remotefile" | diff - /tmp/localfile

2. Outputting your microphone to a remote computer's speaker

dd if=/dev/dsp | ssh -c arcfour -C username@host dd of=/dev/dsp

Great service that serves a real need (Craigslist/StubHub/etc are all a royal pain to navigate and utilize).

The site has a sophisticated, clean design, one which seems to assume that its visitors will plunge in and begin searching for seats with little hand-holding.

http://en.wikipedia.org/wiki/CubeSat

http://stuffwhitepeoplelike.com/2008/07/31/106-facebook/

ROS (rate of speech) is one of the primary contributors to this variably and some recent research (http://www.ee.columbia.edu/~dpwe/papers/PfauR98-spkrate.pdf) has shown that good estimates of speaking rate can be obtained using vowel detection as vowels in general correspond to syllable nuclei.

I wonder if Sukhotin's algorithm could be modified to improve upon this work?

http://cityroom.blogs.nytimes.com/2010/06/29/bill-could-make...

This article (http://seattleweb.intel-research.net/people/lamarca/pubs/pap...) coming out of Intel argues that it is also difficult to implement more sophisticated structures on top of a distributed key/value. The author's main point is that a few specialized applications can and have been built on a plain distributed key/value store, but most applications have ended up having to customize the key/value store's internals to achieve their functional or performance goals.

From the little bit I have read about Membase it looks well positioned to bring simple distributed key/values stores to the next level and back into the lime light.

- Jason Fried & David Heinemeier Hansson, "Rework"

The incentives for people on Wall Street got so screwed up, that the people who worked there became blinded to their own long term interests because the short term interests were so overpowering. So they behaved in ways that were antithetical to their own long term interests.

CouchDB is great but don't get me wrong ORMs like ActiveRecord and DataMapper have done a lot to to ease the pain and abstract away the nastiness of SQL. It’s not enough though. It’s like treating the symptoms and not the underlying condition. You still have to worry about joins, normalization, and other artifacts from relational databases. These issues leak their way up into your models where they don’t belong, and obscure more important logic. All of this isn’t an issue with CouchDB, and that’s the biggest selling point for me.

"For a brief period of time, MySpace was the site where everyone kept their profile and managed their friendships. But soon, the service began to attract fake profiles, the wrong kind of white people, and struggling musicians. In real world terms, these three developments would be equivalent to a check cashing store, a TGIFridays, and a housing project."

- Christian Lander, "Stuff White People Like" - #106 Facebook http://stuffwhitepeoplelike.com/2008/07/31/106-facebook/

http://www.forbes.com/forbes/2010/0607/opinions-houston-immi...

recently that had a narrower focus (Houston) but touches on many of the same topics ... innovation, job growth and immigration ... and how they have helped Texas stay ahead of the curve during the recession.

When compared against its main rival Hulu (as in this post http://www.readwriteweb.com/archives/10_reasons_why_joost_fa...) it becomes clear why Joost's user experience also encumbered its own success.

1. Poor grammar and bad writing are often a sign of poor comprehension.

2. Good documentation takes time.

3. Deep expertise is not automatically a prerequisite for good documentation.

4. Don’t let working cultures that put too great a premium on knowing everything dominate - i.e. being 'in the know' should be a tool for helping others up rather than beating them down.

http://perspectives.mvdirona.com/2010/06/14/SeaMicroReleases...

Most of these features can be added to Sinatra already, either manually or by selecting from a wide assortment of independent plugins. Padrino, on the other hand, provides a standard suite of functionality that, hopefully, will continue to be improved as a whole over time. It feels a lot like Ramaze (http://ramaze.net/) but with the similar functionality wrapped around Sinatra instead.

While a lot of factors go into determining whether a language is readable I have always felt the most obvious is familiarity. The human mind is very good at adaptation, and often it’s astonishing what we will perceive as "normal." Familiarity only comes from constant exposure, though, which means that languages with relatively simple syntax become familiar more quickly. Lisp is at one extreme, with only one syntactic construct. It’s very easy to become familiar with Lisp, although grasping the large Common Lisp standard library is another matter. I tend to agree with the author that C++ is a language at the other extreme. Most C++ coders I have encountered use only a relatively small subset of the C++ language. Worse yet, everyone uses a slightly different subset.

Of course, the biggest impact on readability comes not from the language, but from the developer. A poor developer can write illegible code in any language. A good developer? I’ve even seen well-written, readable Visual Basic code (once).

There is also a great need for Software Engineers/Mathematicians to improve the analysis software and the algorithms behind them (primarily string matching) to account for advances in the "chemistry" that companies like ABi and Illumina are making in regards to their sequencing technology.

These are both just on the "production" side of the process - i.e. the processes and people that produce the first round of analysis and statistics from the raw read data (sets of As, Gs, Ts and Cs). Further analysis that looks for SNPs (single nucleotide polymorphisms, what Wade calls 'variant DNA units'), carries out genome annotation and eventually attempts to statistical link both of those results and numerous others to disease traits is carried around by teams of programmers and biologists/geneticists. However, as the data becomes increasingly large and complex so too does the role programmers and clever software play.

He suggests creating a "to-stop" list - a list of all the things that are sucking away your energy and are wasting your time. He suggests figuring out which of those things is having the biggest negative impact on you doing the stuff you really want to do and tackling that thing head on each day.

As a computer scientist working at one of the major genome centers mentioned in the NYT I can attest to ben1040's claim.

In the last five years alone because of technological advances in sequencing technology we have moved from talking about genomic data in megabases (Mb) to gigabases (Gb). Illumina newest HighSeq sequencing technology is capable of 300 Gb per run, 10x more than there competitor ABi's SOLiD instruments which were released as little as 2 years ago!

Any talk of partnering with NHL, MLB, NBA, etc. to stream live audio/video of games?

With an increasing number of smart phones packing a powerful camera what about serving as a platform for fans to share their own media content from games - like photos?