Axel Ingadi ingadi

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

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.

There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules directory) as well as files that are generated (and regenerated) as artifacts of a build process.

All other files should be in your own global gitignore file:

Create a file called .gitignore in your home directory and add any filepath patterns you want to ignore.
Tell git where your global gitignore file is.

Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute .config/git/ignore for .gitignore in your home directory, if you prefer.

How to have specific .gitignore for each git branch

Objective

My objective is to have some production files ignored on specific branches. Git doesn't allow to do it.

Solution

My solution is to make a general .gitignore file and add .gitignore.branch_name files for the branches I want to add specific file exclusion. I'll use post-checkout hook to copy those .gitignore.branch_name in place of .git/info/exclude each time I go to the branch with git checkout branch_name.

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/

What's an Effective Engineer?

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages

	#!/bin/bash

	# Put this file at: .git/hooks/post-checkout
	# and make it executable
	# You can install it system wide too, see http://stackoverflow.com/a/2293578/685587

	PREV_COMMIT=$1
	POST_COMMIT=$2

	NOCOLOR='\e[0m'

	# Compiled source #
	###################
	*.com
	*.class
	*.dll
	*.exe
	*.o
	*.so

	# Packages #

	#!/bin/sh

	# qemu-img create -f qcow2 mac_hdd.img 64G
	# echo 1 > /sys/module/kvm/parameters/ignore_msrs
	#
	# Type the following after boot,
	# -v "KernelBooter_kexts"="Yes" "CsrActiveConfig"="103"
	#
	# printf 'DE:AD:BE:EF:%02X:%02X\n' $((RANDOM%256)) $((RANDOM%256))
	#

	/* ----------------------------------------- *
	Lazy List Implementation
	* ----------------------------------------- */

	// Haskell-like infinite List, implemented with es6 generators

	// Lazyness lets you do crazy stuff like
	List.range(0, Infinity)
	.drop(1000)
	.map(n => -n)