1,327 karma · joined March 3, 2013
https://www.sacbee.com/news/investigations/the-public-eye/ar...
But one valuable reason to use something like UPX is that you can attach a crappy and thus inexpensive disk to servers that you're not using for actual storage. Compression on disk lets you load from a slow disk faster, and of you weren't paging to disk anyway then UPX doesn't have much of a cost.
But if you're on a traditional desktop operating system, UPX will increase your effective memory footprint, and force writing to swap instead of merely dropping pages. On Android, which doesn't swap, you'll significantly increase your memory footprint.
There's also tools like [2], where you can tell a mutex to spin if the current lock holder is actively running (as opposed to blocked or preempted), to get the best of both worlds.
[1] https://blog.postmates.com/why-spinlocks-are-bad-on-ios-b69f... [2] https://lwn.net/Articles/724384/
A carbon tax designed to fairly internalize externalities will not really please protectionists.
Splitting code across multiple files when there's no actual reusability or abstraction driving the split makes it harder to follow the flow of logic. In particular, 750 lines is not so much that there's obviously a missing abstraction lurking there.
That's how you end up with stuff like OS X's "no really, fsync" param [1], or Motorola shipping nobarrier on their phones. [2]
[1] https://github.com/google/leveldb/issues/203#issuecomment-55...
[2] http://taras.glek.net/post/Followup-on-Pixel-vs-Moto:fsync/
1. Lots of options visible up front. Instead of reading tons of text, or guessing at hieroglyphics, you could find the tool to accomplish your desired task visually - if you want to change text color, look for the color picker.
1. Big improvement to mouse navigation. Navigating nested menus is a bit like playing Operation - you position your cursor on the item you want, then slide it horizontally to the next menu that expanded. But if you drift too far vertically, which was easy to do of you had a disability or a crappy trackpad, you have to start again. With the ribbon, there was no destructive effect to moving the mouse around without clicking. You could always take the shortest path to whatever you wanted to click on.
1. Big improvement to keyboard navigation. Tap the alt key, and every affordance in the ribbon displays its keyboard shortcut. This allowed the same exploratory navigation as the mouse, but in a way that built muscle memory and avoided RSI.
Of course it was a large change, but the ribbon was an amazing improvement.
https://github.com/google/guava/commit/4e41d621c3f413eb31da2...
Almost any work on compilers will involve good working familiarity with graphs
Work with concurrency will tend to involve linked data structures, like treiber stacks, or modeling computations as directed acyclic graphs of data dependencies
Working in a memory constrained environment tends to involve data structures and algorithms tailored to that domain, etc.
Now it's totally true that many algorithms questions just reduce to brain teasers, or are so esoteric and interview-specialized (Find out if this linked list has a cycle in O(1) space!) that they only serve to stoke the egos of the interviewer. But I wouldn't say that using algorithms or implementing a data structure is a skill that only exists to facilitate interviewing - and being able to explain your thought process as you work is really important when making contributions to other teams' code. I try to focus my interview questions on miniature versions of problems I've actually had to solve in the course of my job. For example, the futex state machine I wrote here:
https://android-review.googlesource.com/c/platform/art/+/810...
If you subtract the interrupt and timeout handling, you have a real problem with a simple, approachable (for someone with some concurrency knowledge) solution, and you only need to know about two futex calls which have simple behavior and are easy to explain in limited time. I wouldn't ask this question of someone looking for a web development position; but then again, I don't interview those candidates because I know nothing about web development. But it's a nice question for someone who listed concurrency on their resume.