Jearvon Dharrie iamjarvo

PKI is based upon two keys (public and private)
Data can be securely encrypted using either the public or private keys
Data can only be decrypted when using the opposite key to that which encrypted the data
Use a Key Generator (e.g. ssh-keygen) to create your public/private keys
These keys are typically stored in ~/.ssh/
- id_rsa (private key; do not share! typically used to decrypt data)
- id_rsa.pub (public key; typically used to encrypt data)

Prologue

I wrote this answer on stackexchange, here: https://stackoverflow.com/posts/12597919/

It was wrongly deleted for containing "proprietary information" years later. I think that's bullshit so I am posting it here. Come at me.

The Question

Amazon is a SOA system with 100s of services (or so says Amazon Chief Technology Officer Werner Vogels). How do they handle build and release?

Overview

This gist is based on the information available at golang/dep, only slightly more terse and annotated with a few notes and links primarily for my own personal benefit. It's public in case this information is helpful to anyone else as well.

I initially advocated Glide for my team and then, more recently, vndr. I've also taken the approach of exerting direct control over what goes into vendor/ in my Dockerfiles, and also work from isolated GOPATH environments on my system per project to ensure that dependencies are explicitly found under vendor/.

At the end of the day, vendoring (and committing vendor/) is about being in control of your dependencies and being able to achieve reproducible builds. While you can achieve this manually, things that are nice to have in a vendoring tool include:

Review checklist

General

Does the code work?
Description of the project status is included.
Code is easily understand.
Code is written following the coding standarts/guidelines (React in our case).
Code is in sync with existing code patterns/technologies.
DRY. Is the same code duplicated more than twice?

Why I don't think Ruby is great

This post was inspired by this post on why the author thinks "Ruby is still great" and this tweet stating that Shopify (and others) are successful because of Rails, not despite it.

Now, let me first give a little background. I've been a Rails programmer since late 2006. Before Rails I went through PHP, ASP and ASP.NET (like most people at the time).

Back pre-2010, Rails was a force-multiplier, and to some degree still is. It provided a completely new way to do web development, including code generation and all the necessary tooling out of the box. The deployment story was sad until Heroku came on the scene, but we suffered through it because Rails solved a real problem.

After over 10 years of dealing with Rails' problems, I'm not so enthusiastic anymore. I believe it is impossible to write a high quality application in Rails. By high quality I mean it satis

FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.

Effective Engineer - Notes

By Edmond Lau
Highly Recommended 👍
http://www.theeffectiveengineer.com/

	SHELL = /bin/bash

	terraform_opts ?=
	terraform_plan_opts ?=

	.PHONY: help
	help::
	@echo
	@echo Infrastructure management using Terraform.
	@echo

	#!/bin/bash
	# from https://chromium.woolyss.com/
	# and https://gist.github.com/addyosmani/5336747
	# and https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md
	sudo apt-get update
	sudo apt-get install software-properties-common
	sudo add-apt-repository ppa:canonical-chromium-builds/stage
	sudo apt-get update
	sudo apt-get install chromium-browser
	chromium-browser --headless --no-sandbox http://example.org/

	package main

	import (
	"context"
	"flag"
	"fmt"
	"log"
	"net/http"
	"os"
	"os/signal"