| /* iPhone */ | |
| @media only screen | |
| and (min-device-width : 320px) | |
| and (max-device-width : 568px) { /* iPhone 5 in portrait & landscape */ | |
| } | |
| @media only screen | |
| and (min-device-width : 320px) | |
| and (max-device-width : 568px) | |
| and (orientation : landscape) { /* iPhone 5 in landscape */ |
Image service - S3 client acess - 1652 ms should allow access to uploaded files by the app - 1041 ms should not allow web access to uploaded files - 392 ms should not allow an unauthorised user to access the bucket - 218 ms
Image service - upload limit - 972 ms should reject uploads if they are over 2MB - 652 ms should allow uploads if they are under 2MB - 320 ms
#uploadFileForPublicAccess - 341 ms
| // TL;DR - Lambda means "function used as data". | |
| // Anonymous function means "function without a name". | |
| // This is one of the relatively few cases where the Wikipedia definition of | |
| // a word, while not entirely wrong, is misleading. Lambdas and anonymous | |
| // functions are distinct ideas. | |
| // These ideas are commonly confused because in many programming languages | |
| // all lambdas are anonymous or vise verse. |
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Fri, 19 Jun 2015 15:17:38 GMT till Sun, 19 Jun 2016 15:17:38 GMT.
Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:
githubUsers
.filter(user => user.followers > 635)
| #/bin/bash | |
| #-- Script to automate https://help.github.com/articles/why-is-git-always-asking-for-my-password | |
| REPO_URL=`git remote -v | grep -m1 '^origin' | sed -Ene's#.*(https://[^[:space:]]*).*#\1#p'` | |
| if [ -z "$REPO_URL" ]; then | |
| echo "-- ERROR: Could not identify Repo url." | |
| echo " It is possible this repo is already using SSH instead of HTTPS." | |
| exit | |
| fi |
| #!/bin/bash | |
| # store the current dir | |
| CUR_DIR=$(pwd) | |
| # Let the person running the script know what's going on. | |
| echo "\n\033[1mPulling in latest changes for all repositories...\033[0m\n" | |
| # Find all git repositories and update it to the master latest revision | |
| for i in $(find . -name ".git" | cut -c 3-); do |
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
| acm.amazonaws.com | |
| alexa-appkit.amazon.com | |
| apigateway.amazonaws.com | |
| application-autoscaling.amazonaws.com | |
| appstream.application-autoscaling.amazonaws.com | |
| appsync.amazonaws.com | |
| athena.amazonaws.com | |
| autoscaling.amazonaws.com | |
| batch.amazonaws.com | |
| channels.lex.amazonaws.com |