| <!-- | |
| This is a sample email taken from https://developers.google.com/gmail/schemas/apps-script-tutorial | |
| and used to test the GMail actions support. | |
| --> | |
| <html> | |
| <head> | |
| <script type="application/ld+json"> | |
| { | |
| "@context": "http://schema.org", | |
| "@type": "EmailMessage", |
| location / { | |
| try_files $uri $uri/ $uri.php?$args; | |
| } | |
| location /l/ { | |
| rewrite ^/l/([a-zA-Z0-9/]+)$ /l.php?i=$1 last; | |
| } | |
| location /t/ { | |
| rewrite ^/t/([a-zA-Z0-9/]+)$ /t.php?i=$1 last; |
| server { | |
| listen 80; | |
| listen [::]:80; | |
| server_name domain.com; | |
| autoindex off; | |
| index index.php index.html; | |
| root /srv/www/domain.com/public; |
| server { | |
| listen 80; | |
| listen [::]:80; | |
| server_name site.com; | |
| root /home/forge/site.com; | |
| # FORGE SSL (DO NOT REMOVE!) | |
| # ssl on; | |
| # ssl_certificate; | |
| # ssl_certificate_key; |
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Tue, 06 Dec 2016 17:06:46 GMT till Wed, 06 Dec 2017 17:06:46 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 > 1000)
| <?php | |
| /* | |
| * Warning! Read and use at your own risk! | |
| * | |
| * This tiny proxy script is completely transparent and it passes | |
| * all requests and headers without any checking of any kind. | |
| * The same happens with JSON data. They are simply forwarded. | |
| * | |
| * This is just an easy and convenient solution for the AJAX |
| <?php | |
| function json_response($message = null, $code = 200) | |
| { | |
| // clear the old headers | |
| header_remove(); | |
| // set the actual code | |
| http_response_code($code); | |
| // set the header to make sure cache is forced | |
| header("Cache-Control: no-transform,public,max-age=300,s-maxage=900"); |
| import S from '@sanity/desk-tool/structure-builder' | |
| import { MdWork, MdAccountBalance, MdCached, MdDashboard, MdSettings, MdMail, MdPerson, MdAssignment, MdDescription, MdShoppingCart, MdLightbulb, MdLocalOffer, MdChatBubble } from 'react-icons/lib/md' | |
| // We filter document types defined in structure to prevent | |
| // them from being listed twice | |
| const hiddenDocTypes = listItem => | |
| !['redirects', 'page', 'newsroom', 'caseStudy', 'product', 'solution', 'site-config', 'contactInfo', 'resource', 'author', 'blog', 'category', 'testimonial'].includes(listItem.getId()) | |
| export default () => | |
| S.list() |
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
| Largest 1000 Cities in America | |
| 2013 popuation data - Biggest US Cities By Population | |
| rank,city,state,population,2000-2013 growth | |
| 1,New York,New York,8405837,4.8% | |
| 2,Los Angeles,California,3884307,4.8% | |
| 3,Chicago,Illinois,2718782,-6.1% | |
| 4,Houston,Texas,2195914,11.0% | |
| 5,Philadelphia,Pennsylvania,1553165,2.6% |