Nick deLannoy cosmicbuffalo

## redis-conditional-set.txt
# Basic benchmarks
# SET key val # 87489.06
# SETRANGE key2 6 "Redis" # 75757.58 req/s
# INCR  key 245 # 70224.72 req/s
# INCRBY key 245 22 # 67114.09 req/s
# EVAL SET key val # 46296.29 req/s

# SETIFHIGHER (set or update key if new value is higher than current) # 41666.67 req/s
# if not exists return OK , if updated return the increment  , if not updated return 0
SCRIPT LOAD "local c = tonumber(redis.call('get', KEYS[1])); if c then if tonumber(ARGV[1]) > c then redis.call('set', KEYS[1], ARGV[1]) return tonumber(ARGV[1]) - c else return 0 end else return redis.call('set', KEYS[1], ARGV[1]) end"

## 20111011_SteveYeggeGooglePlatformRant.md

      
        
          
            
              
              1 file
            
          
          
            
              
              363 forks
            
          
          
            
              
              60 comments
            
          
          
            
              
              2540 stars
            
          
        
        
          
              
          
          
            
                chitchcock
                / 20111011_SteveYeggeGooglePlatformRant.md
            
            
              Created
              October 12, 2011 15:53
            
              
                Stevey's Google Platforms Rant
              
          
        
      
        
  
      
    Stevey's Google Platforms Rant

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 real
	# Basic benchmarks
	# SET key val # 87489.06
	# SETRANGE key2 6 "Redis" # 75757.58 req/s
	# INCR key 245 # 70224.72 req/s
	# INCRBY key 245 22 # 67114.09 req/s
	# EVAL SET key val # 46296.29 req/s

	# SETIFHIGHER (set or update key if new value is higher than current) # 41666.67 req/s
	# if not exists return OK , if updated return the increment , if not updated return 0
	SCRIPT LOAD "local c = tonumber(redis.call('get', KEYS[1])); if c then if tonumber(ARGV[1]) > c then redis.call('set', KEYS[1], ARGV[1]) return tonumber(ARGV[1]) - c else return 0 end else return redis.call('set', KEYS[1], ARGV[1]) end"