hongkongkiwi

#!/bin/sh +ux
# We set the sh +ux flags so that we error on undefined variables and error on bad commands

help() {
  echo >&2 "$0 [-f] [-p] [-q] [<priv_key_file>] [<key_type>] [<key_comment>]"
  echo >&2
  echo >&2 "-q / --quiet to silent all output (except -p if passed)"
  echo >&2 "-p / --pubkey to output public key after generation"
  echo >&2 "-f / --force to force replacing existing key"
  echo >&2

tzmartin

Awesome SVG Icons

A nice list of icon sets that can be used as web fonts. Handy for building Electron apps too.

Name	URL	Version	License	Created By	Icon Cnt	Source	Url1	Url2
Brandico	https://github.com/fontello/brandico.font	2014.04.07	SIL	Crowdsourced, for Fontello project	45	http://fontello.com/

wojteklu

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

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

Design rules