Dimitri yatmanov

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

Update HISTORY.md
Commit the changes:

git add HISTORY.md
git commit -m "Changelog for upcoming release 0.1.1."

Update version number (can also be minor or major)

bumpversion patch

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

create tasks T{NNNN} asign them
create a branch with name like "T{NNNN}-boo-hoo"
git checkout -b T1234-boo-foo
commit changes on that branch until it gets ready to be reviewed
git commit -am 'first'
git commit -am 'now it works'
check if it's lint free (NOTE: it runs lint against only modified files)
arc lint
push a review request to the server. This will create a diff with id D{NNNN}
arc diff

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

The use of __main__.py to create executables

myprojectfolder/
    |_ __main__.py
    |_ __init__.py

Being __main__.py:

print("Hello")

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

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

	from django.core.management.commands.shell import Command as ShellCommand
	import os


	class Command(ShellCommand):
	shells = ShellCommand.shells.append('ptpython')

	def ptpython(self):
	try:
	# old ptpython

	"""Example to cancel a set of asyncio coroutines (futures),
	using one coroutine to signal the event loop to stop.
	"""

	import asyncio
	import logging
	from datetime import datetime
	from concurrent.futures import CancelledError