beliu

Thanks for the feedback; we're working on site speed as a top priority. The examples are similar to the usages feature from your IDE, but 1) the examples are drawn from all the open-source code we've indexed online and 2) we support non-statically-typed languages like Python, JS, and Ruby.

I find it surprising that in 2014, most of the tools we use to read code treat it mostly like any other text. With the exception of some IDEs for some languages (e.g., Eclipse and Java), very few apps for browsing code actually understand its structure, i.e., the hierarchy of symbols and namespaces and the implicit graph defined by module imports, function calls, type references, etc. We're relying more and more on external, often open-source libraries, and are therefore spending more and more of our time reading through other people's code. Yet the tools don't seem to have caught up.

Might I suggest looking at https://sourcegraph.com? Currently it's just code search, and doesn't do code review. But it does understand the code at a function/class/module level. And that makes it fundamentally different from a lot of other code reading tools out there that just treat code as text. For code search, that means it can do things like show you how other people actually call a given function. For code review, it would make it possible to reason about changes to functions/classes/packages instead of lines of text. (Disclaimer: I'm one of the creators of Sourcegraph; would love to hear your feedback)

This is a good point, and one I forgot to address.

We would never ask to see proprietary source code. Hopefully, a candidate would have a side project or open source work they're willing to share. If not, we'd definitely work around this. For team projects, we'd ask them to describe their contribution. So far, this hasn't been a big problem, but we're still iterating and making the process better!

Has anyone tried out python in postgres? (http://www.postgresql.org/docs/9.0/static/plpython.html). In the past, I've tried to avoid stored procs for the reasons mentioned above, but have not yet had the chance to try out python and would be interested in hearing about people's experiences with it.

We used Piazza heavily inside Stanford CS and it was definitely a big step up from mailing lists and pine. Am curious to see how well this compares to StackOverflow Careers, both from a recruiter and candidate perspective.

prezjordan, you should check out Sourcegraph (https://sourcegraph.com). It shows you how many other projects/people actually use a library and how they use it (code snippets).

[0]: https://sourcegraph.com/github.com/jdan/cleaver [1]: https://sourcegraph.com/github.com/numpy/numpy

disclaimer: I am one of the creators of Sourcegraph and would love to hear what you think about it!