made with esnextbin
View Instructions
# | |
# @author Jonathon byrd | |
# | |
############################################################ | |
# first things first, set your iptables for a web server. If you jack these | |
# up you don't want to have to re-install your os after doing much more. | |
# @see http://www.thegeekstuff.com/2011/06/iptables-rules-examples/ | |
# and | |
# @see https://help.ubuntu.com/community/IptablesHowTo |
View dialogue.js
/** @jsx hJSX */ | |
import {hJSX} from '@cycle/dom'; | |
const DIALOGUE_NAME = `dialogue`; | |
let idSuffix = 0; | |
function makeCycleId() { | |
return `${DIALOGUE_NAME}-${idSuffix++}`; |
View gh-labels.sh
#!/usr/bin/env bash | |
echo -n "Username: " | |
read USER | |
echo -n "Password: " | |
read -s PASS | |
echo -n "Repo (e.g., foo/bar): " | |
read REPO |
View esnextbin.md
made with esnextbin
View esnextbin.md
made with esnextbin
View esnextbin.md
made with esnextbin
View esnextbin.md
made with esnextbin
View esnextbin.md
made with esnextbin
View functional-typescript-naming-convention.md
Functional TypeScript Naming Convention
Motivation
Giving names in a language that doesn't support function overloading is a challenging task. It is, however, important to follow some standards to avoid naming conflicts, misleading names, and also to maintain a unified style. The following rules were developed to encourage programming in a functional style in TypeScript, but can also be used anywhere else where it makes sense.
Disclaimer
The following rules are work in progress, and far from being complete, your questions and ideas are welcome. Please leave a comment.
Goals
- Avoid naming conflicts and misleading names.
OlderNewer