I love Papers but they've been ridiculously slow with retina support; I wouldn't mention it, except it's the easy things that still haven't been done, such as coloured circles for tags, while more complicated things (many icons/artwork etc.) were done ages ago.
They released a major new version (Papers 3) just under a year ago. One of those 'fresh start' kinda releases; a re-think of what a reference app should be like, and substantially different from Papers 2. I still haven't upgraded because it doesn't do much more than Papers 2 did, but if you're coming to the product for the first time, it really is a great release. Highly recommended. Definitely the best Mac client out there, and they have a good iOS app too, along with solid Dropbox syncing. (Haven't tried their Windows version.)
Ah, they've moved since they started. Their new offices are indeed in London, though if you look at the copyright notice on the footer of that page you'll see it has a Netherlands address. Their careers page [1] does say their new offices are in London.
When they started, the two founders were both still mainly post-docs at the Netherlands Cancer Institute [2], and that's what I remembered, reinforced by the copyright notice I mentioned above.
Also, you don't have to use Eclipse or Android Studio at all if you don't want to. You can use whatever text editor and whatever build system floats your boat (ant and gradle are common).
The only time I use either of the Android IDEs (Android Studio, because Eclipse is horrible) is when I need to do on-device visual debugging; otherwise I just do command-line builds and deploy using adb.
The history is a property of the shell (bash, zsh), not the terminal.
Edit: I wrote a thing here about the difficulty of carrying history across terminal sessions and how can you associate a tab you open now with a tab you had open in a previous session, but then I realised that I misread your post.
I would expect the answer in the posted link to work. The 'share_history' option, when set, tells zsh to reread the history file before performing history lookups.
Maybe try the set-local-history option documented here?
Interviews suck, as incidentally does most of higher education. They exist for very well-established reasons, though, and it might be a wiser idea to try to improve them incrementally than to self-ostracise by outright ignoring them.
Anyway (as per my other comment in this thread) I maintain a list of interview resources for programmers (oriented towards companies like G/Fb): https://github.com/andreis/interview
If you want to fix fridges, that's perfectly fine, but at least try to understand why the people who build them might not be interested in hiring you.
Anyway, here's a list of interview resources for programmers that I maintain (oriented towards companies like G/Fb): https://github.com/andreis/interview
