mgaw

It seems they are deprecating their standalone code review tool Upsource in favor of the code review tool that's integrated into Space.

Upsource is nice because it allows opening a review for a set of commits which aren't necessarily continuous. This way, multiple people can work on the same branch at the same time, and open a review for their respective commits afterwards. You don't need to wait for your coworker to have their review approved and their branch merged before you can start building on their work.

As far as I know, the other popular review tools (e.g. Github pull requests) only support reviews for entire branches.

Does anybody know another review tool which allows commit-based reviews as Upsource and Space do?

There is also `vidir` which is part of `moreutils`:

https://joeyh.name/code/moreutils/

Here is a recording showing Jobs telling the story: https://youtube.com/watch?v=ob_GX50Za6c

Hm I would say writing an algorithm is both programming-related and CS-related.

For me there are two reasons:

(1) We want to hire people who are able to solve programming-related problems. Now how do you find out if a candidate can do this? Looking at their CV doesn't tell you much. You can build up a long impressive CV without being able to program. So it would be nice to see them solve a problem right here and now.

Ideally, that would be a problem of the type you would often encounter in your actual work. But there are few programming-only problems in my work. And the hard ones are about designing a larger part of a system, or fitting something new into the context of something old, or trying to understand some old code to be able to adapt it.

My point is: All of these take a massive amount of context into account. Giving a candidate all that context would take weeks.

An algorithm challenge works because it has a good ratio of "time it takes to explain the problem" to "the problem is actually non-trivial to solve".

(2) We do these algorithm questions on a whiteboard, with one interviewer also standing and talking through the development of the solution with the candidate. I believe this gives me a sense of whether I can and want to work together with the candidate either on an actual whiteboard when sketching solutions to problems or when pairing.

Here is one for Ruby: https://rubular.com/

Yes, according to https://mobile.twitter.com/methode/status/910435076613328896

(@methode works for Google)

Ah, I see. Thanks.

This is doublespeak.