made with esnextbin
Frikki
/ Instructions
Created
October 22, 2013 05:32
— forked from jonathonbyrdziak/Instructions
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # | |
| # @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 |
Frikki
/ dialogue.js
Last active
October 3, 2017 08:34
Simple Cycle.js (Nested) Dialogue with MVI Example
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /** @jsx hJSX */ | |
| import {hJSX} from '@cycle/dom'; | |
| const DIALOGUE_NAME = `dialogue`; | |
| let idSuffix = 0; | |
| function makeCycleId() { | |
| return `${DIALOGUE_NAME}-${idSuffix++}`; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/usr/bin/env bash | |
| echo -n "Username: " | |
| read USER | |
| echo -n "Password: " | |
| read -s PASS | |
| echo -n "Repo (e.g., foo/bar): " | |
| read REPO |
made with esnextbin
made with esnextbin
made with esnextbin
made with esnextbin
made with esnextbin
Frikki
/ functional-typescript-naming-convention.md
Last active
March 18, 2018 17:49
Functional TypeScript naming convention.
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.
The following rules are work in progress, and far from being complete, your questions and ideas are welcome. Please leave a comment.
- Avoid naming conflicts and misleading names.
OlderNewer