Mikael Vesavuori mikaelvesavuori

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

Not all random values are created equal - for security-related code, you need a specific kind of random value.

A summary of this article, if you don't want to read the entire thing:

Don't use Math.random(). There are extremely few cases where Math.random() is the right answer. Don't use it, unless you've read this entire article, and determined that it's necessary for your case.
Don't use crypto.getRandomBytes directly. While it's a CSPRNG, it's easy to bias the result when 'transforming' it, such that the output becomes more predictable.
If you want to generate random tokens or API keys: Use uuid, specifically the uuid.v4() method. Avoid node-uuid - it's not the same package, and doesn't produce reliably secure random values.
If you want to generate random numbers in a range: Use random-number-csprng.

You should seriously consider reading the entire article, though - it's

These are instructions for setting up git to authenticate with GitHub when you have 2-factor authentication set up. This authentication should be inherited by any GUI client you are using. These are intentionally brief instructions, with links to more detail in the appropriate places.

Download and install the git command-line client (if required).

Open the git bash window and introduce yourself to git (if required):

git config --global user.name 'Firstname Lastname'
git config --global user.email '[email protected]'

git checkout --orphan future-master
git add -A  # Add all files and commit them
git commit
git branch -D master  # Deletes the master branch
git branch -m master  # Rename the current branch to master
git push -f origin master  # Force push master branch to github
git gc --aggressive --prune=all     # remove the old files

S3 Static Sites

⚠ This post is fairly old. I don't keep it up to date. Be sure to see comments where some people have posted updates

What this will cover

Host a static website at S3
Redirect www.website.com to website.com
Website can be an SPA (requiring all requests to return index.html)
Free AWS SSL certs
Deployment with CDN invalidation

0.1. References
0.2. Other cheatsheets
0.3. Manage multiple gcloud config configurations
- 0.3.1. Switch gcloud context with gcloud config
0.4. Credentials
0.5. info
0.6. projects
0.7. zones & regions
0.8. Organization
0.9. billing

Read data from a public bucket using gzip compression.

First bit of code opens a bucket and lists contents.

Next reads a gzip json file and deserializes it to an array. Please note not very efficient for a large array since the byte array is loaded into memory.

package main

import (
	"compress/gzip"

Scope	Description	User repo:read	User repo:write	User repo:admin
(no scope)	Access public information (read-only)
user	Update all user data
user:email	Access user email addresses (read-only)
user:follow	Follow and unfollow users
public_repo	Access public repositories		I	I
repo	Full control of private repositories	C	CI	CI
repo_deployment	Access deployment status

	The primary goal is to swap command and option.

	The secondary goal is to remap Caps Lock to Control.

	The tertiary goal is to share modifier keys across keyboards, so you can emacs with two keyboards.

	The following instructions are good as of 2016-08-24, for OS X El Capitan 10.11.6.
	Mac OS Sierra broke Seil support; Seil instructs us to consider Karabiner Elements.
	But when Karabiner Elements swaps command and option, it does it for all keyboards;
	meaning the native keyboard also gets its command and option swapped, which is bad!

	// Ignore those pesky styles
	require('ignore-styles');

	// Set up babel to do its thing... env for the latest toys, react-app for CRA
	require('babel-register')({
	ignore: /\/(build\|node_modules)\//,
	presets: ['env', 'react-app']
	});

	// Now that the nonsense is over... load up the server entry point