catechu's comments

While anything that brings more talent into the programming world is a good thing, I find it disappointing when I see such lists encourage cursory understanding like this. While it does have a section on "Becoming the Master", I think that prefacing the section with "[i]f you're still yearning for more" doesn't have the normative force I find in similar but more inspiring works such as Raymond's "How to Become a Hacker."

Personally, reading the following in Raymond's essay many years ago impressed me with the importance of mastery and motivated much of my attitude toward programming:

"Learning to program is like learning to write good natural language. The best way to do it is to read some stuff written by masters of the form, write some things yourself, read a lot more, write a little more, read a lot more, write some more ... and repeat until your writing begins to develop the kind of strength and economy you see in your models."

The focus on mastery is critical to any hacker's path, in my opinion -- it is not an option.

That said, kudos on encouraging more hackery. :)

How can you check if nothing happened?

I wondered why this is legal and my doubts were resolved in the FAQ.

"Having the winnings become philanthropic gifts solves the legal problem and also introduces an appropriate element of service and generosity to the whole process."

Useful presentation, though I don't know how reliant Google still is on MapReduce for search.

There's a slide in there "Numbers Everyone Should Know" that deserves its title -- things like 10,000,000ns for a disk seek.

I would say the same, but I think its absence has reduced me to tears enough in the past, so I'll pass. :)

I don't think Jobs is concerned about retrospectively predicting the successes he had. Rather, I think he wants to emphasize their inherent unpredictability, together with the assertion that such unpredictability doesn't matter. So it's not quite hindsight bias.

Would the magnetic field required be detectable by other means, offsetting the stealth?

If not, that's pretty neat. Now to make an iPhone app for it...

There's certainly an air to having your dot sketch in the WSJ from what I hear, though I imagine that's faded after its years of remodeling itself and its time under new ownership. That said, the difficulties with using an algorithmic filter for creating this stipple effect are, based on my past attempts:

(1) robustness to lighting conditions

(2) recognition of continuous shapes, such as hats (captured well in [1])

(3) avoiding stipple effect on facial features (e.g. lips, eyes)

I'm not saying it's impossible, just that I haven't been clever enough to encode it correctly. :)

[1] http://gazeandstare.com/pic/nolinovak_01.gif

Her portfolio seems to be here: http://www.ecargnfx.com/grace_portfolio.pdf.

I agree -- I see no problem other than their potentially clogging the main page. (I voted in support.)

In addition to the mutable records mentioned in the post, arrays and references are also mutable in OCaml. Aside from objects, I consider this impurity to be the biggest difference in practice. Mutability allows simple OCaml solutions to problems that would otherwise demand monadic gymnastics in Haskell.

FWIW, I've also never been able to design a large project in Haskell (a la darcs), whereas I could write fairly large projects in OCaml without much awkwardness. I suspect the ability to "cheat" with mutability outweighs in practical terms the theoretical elegance and enjoyment of programming in Haskell.

Unity looks nice, but its improvements over GNOME seem to be mainly cosmetic -- not compelling enough to pull me away from the simplicity of dwm (http://dwm.suckless.org/), at least not yet.

Students who've taken systems programming classes (e.g. Operating Systems) would be your best bet -- in my experience, most low-level programming is shafted to those classes, except in the cases where a professor arbitrarily requires C, which doesn't necessarily happen in algorithms classes either.

But even better would be to find students who hack on open-source projects written in C (e.g. Linux-related efforts) -- that's much more representative of a graduating student's ability to be productive using C. There are a lot of students working on such projects, and it might be worth starting there.

That's a great point -- currently, I'm in the process of scraping specs from other sites, and I really like your idea of putting a layer of understanding over that to simplify the display for the user.

Kind of like Google Squared, but easier to generate the table.

I'd like to check it out, but it doesn't seem to be up.

I wanted to be able to see products on Amazon side-by-side with their pros and cons: http://silvos.com.

I need to add more products, product specs, and fix the way the pros/cons work, but I'm already using it to start thinking about which digital camera to get.

Ouch. In retrospect, "Falling Sky Entertainment" was a good name choice for the production company.

I'm not familiar with Arc's internals or the effect that this would have in the context of GC, but as a hack, perhaps you could assign multiple people to a single interpreter instance, prepend prefixes to symbols to avoid collisions before evaluating (e.g. user_1_total, user_1_total, user_2_total), and make each user optionally aware of commands from other users on that instance (e.g. implemented as in-browser chat), letting individual evaluations block each other -- I doubt anyone's doing anything particularly heavy-duty or time-sensitive on your server.

This is convoluted and fragile, but if I wanted to roll out "sandboxes" on limited hardware I'd start with something like this.

Interesting premise! Trying the description itself:

"Enter a paragraph of text. We'll run it through our highly sophisticated algorithms* and output a lovely, totally original piece of text."

rather amusingly yields:

"come in a piece of writing of text. We'll run it done our extremely advanced algorithms* and end product a lovely, wholly unoriginal part of text."

As a next step you could encode rules from Strunk & White [Strunk: http://www.bartleby.com/141/].