Zac evilkirin

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

Chapter 1 - Object Oriented Design

The purpose of design is to allow you to do design later, and it's primary goal is to reduce the cost of change.

SOLID Design:

Single Responsibility Principle: a class should have only a single responsibility
Open-Closed Principle: Software entities should be open for extension, but closed for modification (inherit instead of modifying existing classes).
Liskov Substitution: Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.
Interface Segregation: Many client-specific interfaces are better than one general-purpose interface.

Rich Hickey on becoming a better developer

Rich Hickey • 3 years ago

Sorry, I have to disagree with the entire premise here.

A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.

Mastery comes from a combination of at least several of the following:

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.

MacOS

Build 3059

MD5: 59bab8f71f8c096cd3f72cd73851515d

Rename it to: Sublime Text

Make it executable with: chmod u+x Sublime\ Text

	Latency Comparison Numbers (~2012)
	----------------------------------
	L1 cache reference 0.5 ns
	Branch mispredict 5 ns
	L2 cache reference 7 ns 14x L1 cache
	Mutex lock/unlock 25 ns
	Main memory reference 100 ns 20x L2 cache, 200x L1 cache
	Compress 1K bytes with Zippy 3,000 ns 3 us
	Send 1K bytes over 1 Gbps network 10,000 ns 10 us
	Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD

	interface List {
	Object first();
	List rest();
	}

	def empty() {
	null
	}

	def singleton(node) {

	ClassLoader classLoader = getClass().getClassLoader();
	// Implies that we're at the top of the hierarchy when null.
	while (classLoader != null) {
	System.out.println("Class/Method Name Here: parent classLoader == " + classLoader.toString());
	// Note that getParent() may require opening up the
	// security settings in the JVM.
	classLoader = classLoader.getParent();
	}
	System.out.println("Class/Method Name Here: parent classLoader == null");

	;; this file is a walkthrough of Moustache features, a web framework for Clojure
	;; https://github.com/cgrand/moustache/tree/master

	;; Moustache allows to declare routes, apply middlewares and dispatch on http methods.
	;; Moustache is compatible with all frameworks built on Ring, including Compojure

	(ns demo
	(:use net.cgrand.moustache)
	(:use [ring.adapter.jetty :only [run-jetty]])) ;; hmmm Ring without servlets