thumper
My cats did not join me in the box.
And when I had to include some multi-line javascript in my code, I found myself feeling a huge loss. First, heredocs seemed to be the only way to make it readable. Second, I'd have to actually run the code and interact with the page to find out if I got the syntax right. It would be awesome if there was a way to make JS into an object in PHP, the way that XHP is done, and have it support some simple sanity checks and easily import JS components (which I suppose Javelin tries to do).
Seriously, we had that exact idea implemented around 1997 -- and it even supported multiple authentications (anonymous worlds, versus worlds with user accounts) all transparently. And it could even do VRML, crowd control, dynamic downloads (so you could link to new worlds), and a built-in world builder.
It seemed that we had thought of everything... And then management took over.
No, Virginia, Perl is not dead. Not as long as there is more than one way to do it, or a hacker trying to finish something that was due yesterday.
Perl, as we know it, might pass from this earth. But the spirit it embodied, that first we should use duct tape to build on the work of others then write glue to make it stick, that getting-things-done was the primary goal --- this is too close to the core of our restless selves. A thousand years from now, there will be some startup somewhere with an urgent need and a hacker that strokes his chin and says, "I think I could write that in Perl[1]..."
[1] replace "perl" with your favorite language. Pick the right tool for the job. Sometimes means "the tool you are most familiar with", but that says more about you than about the language.
As I've "matured", I feel like my raw speed is slowing down. I think that there are a lot of factors in that, like working on much more challenging problems, and switching back and forth between too many languages (so that I don't know any one quite as well).
Really, I think it's better to worry about working on stuff that you love, rather than how fast you're doing it.
The Dark Side of Negotiating
My take is that the code doesn't specifically limit the exception to my job function; it's broadly worded to cover the whole of the business. And the UC works on so many areas of research that this essentially means that you can't work anywhere else at the same time if that other work requires any kind of confidentiality.
I tried to engage the IP department at my school about this, but got shuffled around and basically told that there are no exceptions or clarifications. They essentially supported this interpretation I have, and referred me to memos that explain the policy in more detail.
What I can't figure out is this: the policy requires that all students submit potential IP to them for evaluation. That includes IP from summer internships. Why are companies okay with this? In practice, I don't believe many (any?) students do this, but the Director stopped answering my emails when I tried to probe this question more deeply.
There isn't a clear cut answer because so much depends on your personality and what you want to get out of life.
What I can definitively say: if you've been out of school for a few years, getting an MS in CS is totally worth it. I learned so much about the "new stuff" that I never got around to when I was working, and the bigger toolbox has already paid off for me.
Beyond that, I sort of agree with other posters, but I'm a little more cynical about the long-term vs short-term aims of academia. I'm finding that my startup sensibilities work well for guiding my efforts in a PhD, but this is because I've come believe that grad school is essentially a machine for conferring reputation from professors to students. Keep in mind that even when your advisor gives you a lot of latitude (and that'll take years), you're still not your own boss... and that can suck if you're older than the average student.
Of course, working in a research lab has similar issues. You don't completely get to set your direction, there's a big bureaucracy, and you have to work hard to get people to understand your work.
Out of everything I've done, being in a startup where we all shared The Dream was the best.
If there's no normalization, then this gives a snapshot about movie popularity... something like a 1-D vertical slice from a visualization like one of these two:
http://www.nytimes.com/interactive/2008/02/23/movies/2008022...
http://xach.com/moviecharts/2008.html
I don't want to knock this new visualization, but I'm wondering what inferences would be safe to draw from the data as presented. It seems like it is most useful for comparing regions to each other; for instance, I was surprised at how varied the movie ordering was for adjacent neighborhoods in Manhattan.
"Three Things Statistics Textbooks Don't Tell You" by Seth Roberts: http://sethroberts.net/about/2005_Three_Things_Statistics_Te...
It's possible that different underlying issues alter the effectiveness, but I think the general advice of "exercise" is a good one. I'd also add that there's potential to hurt yourself more, so I'd rewrite the parent comment as "you should also see a physiotherapist."
On the page views signal - there was a great paper in the last few years that came up with a way to estimate it from multiple other data sources (eg, Alexa). I don't remember the title, but it was an impressive bit of stitching together. If I had the time/money/resources, I would love to get that as a signal in our work and see if it helps. I'm not 100% convinced it would, because of vandalism I've seen which lasted for years on a somewhat popular page -- so even many eyes does not help if no one will take action to fix incorrect data.
I am one of the researchers on this project, and there are no "resources" which are being made available to us -- it's been something of an uphill battle to do more than just talk. We came up with our idea in January 2006, and spent the year implementing it. Even now, with this attention and with it being open source, there are no volunteers stepping forward to help make it a reality on the Wikipedia itself. We receive very little funding (from CITRUS and LANL, not Wikipedia), and I pay my own tuition from my side-job. Our research group has been really focused this last year to make the code "production ready" instead of just research code, but don't forget that we are academics -- it's difficult to justify our spending time this way, except that we truly believe in the project.
In terms of "credit for the idea", the earliest published work that I have seen is the "Puppy Smoothies" article in First Monday ( http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/ar... ) We cited that and every other blog posting (unusual for an academic paper!) we could find in our first paper. You'll see that there are actually several that existed at the time, but the real issue is in finding the man power to implement the ideas.