cosbynator

I had an on-campus interview for an internship years ago that contrasts this a bit. It was about 30 minutes and there was no second interview. There were absolutely no technical questions. I was asked about whether I had experience with Apple products and development and the interviewer wasn't too offended when I said no. Absolutely no coding. The interviewer didn't seem to really care about the job description that was posted.

I was asked about some problem solving I had to do at a previous internship and I talked about how setjmp/longjmp saved my skin once. The interviewer seemed more pleased in the fact that I was excited about the solution than the fact that I had one.

Unlike you, I found it refreshing. I got the impression that they cared more about passion than obscure technical answers. In the end, I took another offer instead but it was a difficult decision to make.

This article has very little content beyond a vague complaint about the keyword 'this' without actually showing of examples of the problem.

It is not as if you have to look far javascript awkwardness - you just have to live with some small but ugly workaround. My guess in this case aliasing "self" to "this" at the top level of deeply nested objects would probably solve the problem.

In his own words: http://twitter.com/#!/ID_AA_Carmack/status/21119808432

I consider myself a decent programmer but I have more trouble reading template heavy C++ than I do haskell code. To me, restrained C++ means keeping the unreadable bits outside the code base and isolated in their own library, like Boost :)

Welzl's algorithm for minimum enclosing disk does it for me. Pick a point, recursively see if it is in the disk without the point - if not, it is part of the definition the minimum enclosing disk (forced to be on the boundary). Randomized, simple, clean and expected O(n).

Not enough people know about it! http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.46....

The info is publicly available, but they are linking it together in a machine readable way. It wouldn't take much to add one of your 'multitude of accounts' and then the information would become more specific (interest wise) and also directly traceable to you.

I'm surprised there is as much interest in this as there is. There is a company often recruiting/advertising around my campus that has been trying to get a Blackberry watch (not just a remote like this) off the ground for a good while now: http://www.getinpulse.com/. Their press seems to be pretty limited in comparison.

It is odd what the eye is drawn to in these situations. Fixed and thank you.

Since we are all adding our own, here's my contribution: Source: http://www.thomasdimson.com/res.tex Results: http://www.thomasdimson.com/res.pdf

The template may lack some negative space but I think it is pretty reasonable. The content is crusty and questionable :)

I can second this as a good way of learning. The Node.js site links to a very readable long polling chat app here: http://github.com/ry/node_chat. I learned the framework by modifying this into an IRC-style party game am now working on mobile clients for it.

This seems to be one of those situations where less popular is more interesting. Logging in and browsing the highlights for books I've read brought up a lot of very good passages (that I sadly barely remember).

I have also had a very positive experience with Amazon after doing two internships with Amazon (one of Seattle and one out of Dublin). One of the few companies around that actually allowed me to design, think and be critical rather than just being cast away into some needless intern project. At my school, they tend to hire as many people that meet their bar rather than setting a quota which is probably why it seems that they are always hiring.

I'm comparing to two other internships - two at a theoretical physics institute in Waterloo and two with Bloomberg in NYC.

It is all Canadian dollars, but they exchange rate is close to par and a six figure salary here is still still relatively large. It is interesting for students because we can see how much a particular professor is 'worth' to the university. I'm not sure if it has any effect on recruiting as the disclosure isn't all that well known.

In Ontario we have some crazy law that forces all public sector salaries over $100,000 to be disclosed. For example, here is Waterloo's: http://uwaterloo.ca/documents/sal2008.php (incidentally with a pretty respected mathematics department).

A little shocking at first, but most of the people are deserving.