Nate W nate-double-u

Exclude node_modules and .git from Backblaze backups on Mac

Edit the file at /Library/Backblaze.bzpkg/bzdata/bzexcluderules_editable.xml.
Add these rules inside the bzexclusions tag:

<!-- Exclude node_modules. -->
<excludefname_rule plat="mac" osVers="*"  ruleIsOptional="t" skipFirstCharThenStartsWith="users/" contains_1="/node_modules/" contains_2="*" doesNotContain="*" endsWith="*" hasFileExtension="*" />
<excludefname_rule plat="mac" osVers="*"  ruleIsOptional="t" skipFirstCharThenStartsWith="users/" contains_1="/.git/" contains_2="*" doesNotContain="*" endsWith="*" hasFileExtension="*" />

VimWiki Cheatsheet

[number] refers to the wiki number, set by the order in your vimrc. The default is 1.

Wiki Management

[number] <leader> ww - open wiki index file
[number] <leader> wt - open wiki index file in new tab
<leader> ws - list and select available wikis
wd - delete wiki page

Gmail and GitHub

How to filter emails from GitHub in Gmail and flag them with labels.

The labels in this document are just examples.

Pull Request

Filter	Label

Commit Message Guidelines

In the last few years, the number of programmers concerned about writing structured commit messages have dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developers during debugging process.

This document borrows some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.

Goals
Proposal
- Commit Message Format

Allowed ``

Installing Node.js with `nvm` to Linux & macOS & WSL

A quick guide on how to setup Node.js development environment.

Install `nvm` for managing Node.js versions

nvm allows installing several versions of Node.js to the same system. Sometimes applications require a certain versions of Node.js to work. Having the flexibility of using specific versions can help.

Open new Terminal window.

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

	import requests
	import os
	import time
	from concurrent.futures import ThreadPoolExecutor, as_completed

	# Get GitHub token from environment variable
	GITHUB_TOKEN = os.environ.get('GITHUB_TOKEN')
	if not GITHUB_TOKEN:
	raise ValueError("Missing GITHUB_TOKEN environment variable")

	# Usage:
	# 1) Ctr+S downloads page to ~/Desktop/books.html
	# 2) Run script
	# 3) Find your books in /tmp/humble_books
	# 4) Read them
	# 5) Profit
	cat ~/Desktop/books.html \|
	grep "https://dl.humble.com" \|
	sed -n -E 's/.data-web\=\"(https://dl.humble.com/([.]+).([a-z]+)?["]+)./\1 \2 \3/p' \|
	sed 's/&/&/g' > /tmp/humble_books_list && cat /tmp/humble_books_list \|

	#!/bin/bash
	# node-reinstall
	# credit:
	# http://stackoverflow.com/a/11178106/2083544
	# https://gist.github.com/brock/5b1b70590e1171c4ab54

	## program version
	## Update versions accordingly. https://github.com/creationix/nvm/releases
	VERSION="0.31.0"

	{ config, lib, pkgs, ... }:

	with lib;

	{
	imports = [
	# ISO image
	<nixpkgs/nixos/modules/installer/cd-dvd/iso-image.nix>
	# Hardware support similar to installer Live CD
	<nixpkgs/nixos/modules/profiles/all-hardware.nix>