echion

Thanks for the easy-to-follow instructions. I could quickly come up with an updated, less-likely-to-bore version ( http://bl.ocks.org/mdengler/a36fac5f10098bb94846 ), and included a version of your instructions and link to your comment.

Releasing the SDK / hardware plans would be an interesting step: early adopters / DIYers can effectively alpha-test the hardware...

Agreed - here's another one (I am not affiliated): https://github.com/renshawbay/

Was that in an earlier version? I can't find that in the article now.

This part implies some kind of answer, right? "They also used the trap to store and then retrieve an image consisting of three stripes".

I'm not sure that answers exactly how the "Reader" work, though.

Insofar as this interview speaks to the relevance of brainteasers to actual software development / engineering, it fails to provide a meaningful topic of conversation. It surprises me that nobody's pointed out that at best the conclusions are relevant to engineering "leadership" performance, rather than -- as I expected for "Google" and "head-hunting" -- coding performance. Sure, people skills and team skill are important, but if you're going to get good at selecting for leadership and ignore selecting for productivity, to the extent they're not related you're not going to be very good at creating and maintaining software. Although software isn't 100% of Google's success and coding productivity isn't 100% of software success, it's pretty important.

In that video the quotes to which I guess you are referring are "[investing] is almost entirely a non-professional role" (08:40), "[Market-making] is a highly professionalized role" (09:13), and "[an arbitrageur is a] highly professional role" (11:22).

I thought the video had something in support of your "price prediction is the hard way to algorithmic profit" statement, but I can't find anything very explicitly in support of that (what I thought was your implication). He kind of implies something like that at 15:00 when he says "we have no idea how [price prediction] works [at longer then a few days in the future", but that's not really very strong.

When you said "active trading on signals [...] is the hard way", did you mean active trading at minute-to-day or greater holding periods? That seems a) right :); but b) slightly at odds with your "it's important to have level II data", since I would have thought that is less important at a hourly-to-day or greater holding period.

parent is right - http://en.wikipedia.org/wiki/Kurt_von_Hammerstein-Equord#cit... and http://en.wikipedia.org/wiki/Kurt_von_Hammerstein-Equord#cit...

How are these data valuable without corrections for other potentially explanatory factors like wealth/GDP, education, etc.?

There are some actual numbers here: http://blogs.msdn.com/b/visualstudio/archive/2012/07/16/impr...

One way is that Rich's example compilation units (forms input at a REPL) don't all exist at the same time, like compilation units that are files often do.

It's a shame he wrote "I'm not about to define design here" just before.

Nice work; donated.

I use PyXLL and it works great.

You're right - especially about 4 - but the absoluteness is in practice: your solutions to 2 and 4 require a critical mass of people to understand the data being modelled (and thus - or perhaps the other way around - the processes creating/manipulating the data) and this is so rare as to be effectively non-existent.

Not really, unfortunately. Good luck.

Thanks for the contact - we generally look for permies so probably aren't compatible with what you'd want. But always worth getting in touch just in case.

Not sure what you thought I was "offering" - just answering the OP.

But I understand your skepticism about the id. I've just been lurking for a while and had no need to post.

I'm london - hedge fund.