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

mash

LIBUV_HOME := $(HOME)/src/github.com/joyent/libuv
LIBUV := $(LIBUV_HOME)/build/Release/libuv.a
INC = $(LIBUV_HOME)/include

all:
	gcc -o main -I$(INC) -Wall main.c $(LIBUV)

PHONY: all

drewsberry

:: Build client
RunUAT BuildCookRun -project="full_path.uproject"^
 -noP4 -platform=Win64^
 -clientconfig=Development -serverconfig=Development^
 -cook -allmaps -build -stage^
 -pak -archive -archivedirectory="Output Directory"

:: Cook client
RunUAT BuildCookRun -project="full_project_path_and_project_name".uproject^
 -noP4 -platform=Win64^

drmalex07

README

Create a template service file at /etc/systemd/system/secure-tunnel@.service. The template parameter will correspond to the name of target host:

[Unit]
Description=Setup a secure tunnel to %I
After=network.target

kbarbary

// Doing the operation:
//
//                         | a a a a |  | y |
// x * A * y = [ x x x x ] | a a a a |  | y |
//                         | a a a a |  | y |
//                         | a a a a |  | y |
//
// with SIMD intrinics (specifically AVX).
//
// adapted from https://gist.github.com/rygorous/4172889

inlife

// Sample for reading a file asynchronously using libuv
// taken from https://www.snip2code.com/Snippet/247423/Sample-for-reading-a-file-asynchronously

#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#include <uv.h>

static uv_fs_t openReq;
static uv_fs_t readReq;

nylonee

{
	"info": {
		"_postman_id": "07c117b0-7200-41b9-94fc-5836a6b08d7b",
		"name": "Kafka Rest Proxy API",
		"description": "Adapted from https://docs.confluent.io/current/kafka-rest/api.html",
		"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
	},
	"item": [
		{
			"name": "v2",

Phate334

version: "3"

services:
  janusgraph:
    image: janusgraph/janusgraph:0.6.2
    container_name: jce-janusgraph
    env_file:
      - janusgraph.env
    ports:
      - "8182:8182"

richiejarvis

#!/usr/bin/env python3
from __future__ import print_function
import sys
import os
import time
import asyncio
from ably import AblyRest
my_path = os.path.abspath(__file__)  # Find the full path of this python script
# get the path location only (excluding script name)
base_dir = my_path[0:my_path.rfind("/")+1]

nymous

Logging setup for FastAPI

This logging setup configures Structlog to output pretty logs in development, and JSON log lines in production.

Then, you can use Structlog loggers or standard logging loggers, and they both will be processed by the Structlog pipeline (see the hello() endpoint for reference). That way any log generated by your dependencies will also be processed and enriched, even if they know nothing about Structlog!

Requests are assigned a correlation ID with the asgi-correlation-id middleware (either captured from incoming request or generated on the fly). All logs are linked to the correlation ID, and to the Datadog trace/span if instrumented. This data "global to the request" is stored in context vars, and automatically added to all logs produced during the request thanks to Structlog. You can add to these "global local variables" at any point in an endpoint with `structlog.contextvars.bind_contextvars(custom