chitchcock

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

ianmackinnon

# gcc -Wall -o match match.c && ./match
#


#include <stdio.h>
#include <string.h>
#include <regex.h>

natereed

import org.junit.Before;
import org.junit.Test;

import java.util.HashMap;
import java.util.Map;

public class CRMClientTest {

    private CRMClient crmClient;
    private StubbedClientHandler clientHandler;

akorobov

public class PkiUtils {
    public static final int MinPassPhraseLength = 4;

    public static List<?> readPemObjects(InputStream is, final String pphrase) 
            throws IOException {
        List<Object> list = new LinkedList<Object>();
        PEMParser pr2 = new PEMParser(new InputStreamReader(is));
        
        JcaPEMKeyConverter converter = new JcaPEMKeyConverter().setProvider("BC");
        JcaX509CertificateConverter certconv = new JcaX509CertificateConverter().setProvider("BC");

aodin

package main

import (
	"encoding/json"
	"io/ioutil"
	"log"
	"net/http"
)

type Message struct {

ymnk

// The following code is from http://www.academicpub.org/PaperInfo.aspx?PaperID=14496 .
import java.math.BigInteger;
import java.security.*;
import java.security.spec.*;
import javax.crypto.KeyAgreement;

public class ECCKeyAgreement {
  public static void main(String[] args) throws Exception {
    KeyPairGenerator kpg;
    kpg = KeyPairGenerator.getInstance("EC","SunEC");

magnetikonline

<?php
// https://gist.github.com/magnetikonline/650e30e485c0f91f2f40

class DumpHTTPRequestToFile {
	public function execute($targetFile) {
		$data = sprintf(
			"%s %s %s\n\nHTTP headers:\n",
			$_SERVER['REQUEST_METHOD'],
			$_SERVER['REQUEST_URI'],
			$_SERVER['SERVER_PROTOCOL']

meoyawn

import android.content.Context;
import android.support.v7.widget.RecyclerView;
import android.util.AttributeSet;
import android.view.View;
import org.jetbrains.annotations.NotNull;
import org.jetbrains.annotations.Nullable;

public class EmptyRecyclerView extends RecyclerView {
  @Nullable View emptyView;

CMCDragonkai

HTTP Streaming (or Chunked vs Store & Forward)

The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.

However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on

puf

package com.google.firebase.zerotoapp;

public class ChatMessage {
    public String name;
    public String message;

    public ChatMessage() {
    }

    public ChatMessage(String name, String message) {