kislayverma

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't really have SREs and they make engineers pretty much do everything,

jayeye

Ugly hack to run chrome in a memory-limited cgroup so it does not kill your workstation
when it tries to consume all available memory.

Put this in /usr/local/bin/cchrome, add that to whatever menu system you are using.

You can verify it worked by running:
grep memory `ps ax | grep chrome | grep -v grep  | awk '{printf "/proc/%s/cgroup\n", $1}'`

This has only been tested on kubuntu desktop. Obviously, if you have not enabled
passwordless-sudo for yourself, create and chmod the cgroup directory from some

prestonp

-- returning updated values and old values by using a sub-expression

update orders
  set type = 'delivery'
  where id = 3767
  returning id, type, (
    select type from orders where id = 3767
  ) as old_type;

SinisterLight

(function quine() { console.log('(' + quine.toString() + ')()') })()