Segmond segmond

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

Kubernetes clusters using preemtible instances

Motivation

People experimenting with kubernetes clusters on the GKE not necessarily have money to keep a full cluster on at all time. GKE clusters can be easily resized, but this still incurs in the full instance cost when the cluster is up.

Google has added preemptible instances that are ideal for many

Reader Macros in Common Lisp

This post also appears on lisper.in.

Reader macros are perhaps not as famous as ordinary macros. While macros are a great way to create your own DSL, reader macros provide even greater flexibility by allowing you to create entirely new syntax on top of Lisp.

Paul Graham explains them very well in [On Lisp][] (Chapter 17, Read-Macros):

The three big moments in a Lisp expression's life are read-time, compile-time, and runtime. Functions are in control at runtime. Macros give us a chance to perform transformations on programs at compile-time. ...read-macros... do their work at read-time.

There are three easy to make mistakes in go. I present them here in the way they are often found in the wild, not in the way that is easiest to understand.

All three of these mistakes have been made in Kubernetes code, getting past code review at least once each that I know of.

Loop variables are scoped outside the loop.

What do these lines do? Make predictions and then scroll down.

func print(pi *int) { fmt.Println(*pi) }

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

Index:

	# see - https://news.ycombinator.com/item?id=41890158
	deepseekcoder2.5.py
	------------------------
	def find_combinations(target_product):
	combinations = []
	for i in range(1, target_product):
	for j in range(i + 1, target_product):
	k = target_product // (i * j)
	if k > j and i * j * k == target_product:
	combinations.append((i, j, k))

	# -- coding: utf-8 --

	""" Deletes all tweets below a certain retweet threshold.
	"""

	import tweepy
	from datetime import datetime

	# Constants
	CONSUMER_KEY = ''

	var r1 = /(\$\|£\|€)\d+(k\|K)/m
	var r2 = /\d+-\d+(k\|K)/m
	var r3 = /\d+(k\|K)\s?(€\|EUR)/m
	var candidates = [r1, r2, r3];
	var linkQueue = []
	var comments = document.getElementsByTagName("tr")
	for (var i in comments) {
	var comment = comments[i];

	if (comment.className && comment.className.indexOf("athing comtr") != -1) {