Add all the files

Author: joeytwiddle

Github_flavoured_markdown.url

@@ -0,0 +1 @@
+https://enterprise.github.com/downloads/en/markdown-cheatsheet.pdf

NPM_NOTES.txt

@@ -0,0 +1,5 @@
+When updating the package (or just updating the README) you must bump the version before you publish.
+
+    npm version patch
+    npm publish
+

SEE_ALSO.url

@@ -0,0 +1 @@
+https://github.com/LeCoupa/awesome-cheatsheets

atop.md

@@ -0,0 +1,31 @@
+# Reading log history
+
+Open today's logfile:
+
+    atop -r
+
+or open yesterday's logfile:
+
+    atop -r y
+
+or open the day before yesterday's logfile:
+
+    atop -r yy
+
+Then jump forwards and backwards in time with <kbd>t</kbd> and <kbd>T</kbd> respectively.
+
+Use <kbd>b</kbd> then `16:20` to jump to a specific time.
+
+
+# Sorting processes
+
+    C – sort in order of cpu consumption (default)
+    M – sort in order of memory usage
+    D – sort in order of disk activity
+    N – sort in order of network activity
+    A – sort in order of most active resource (auto mode)
+
+
+# Sources
+
+- https://haydenjames.io/use-atop-linux-server-performance-analysis/

contrib/MOVING_CLI_NOTES.txt

@@ -0,0 +1 @@
+On iTerm2, Shift-Left and Shift-Right jump words

contrib/PhotoshopCS6_cheatsheet_zerolag.com_filled_256_colors.png

@@ -0,0 +1 @@
+Subproject commit 7424bb030d032a9a4dd53ef2a2573468f43eddb5

contrib/kubernetes-cheatsheet.pdf

@@ -0,0 +1,11 @@
+    git init <repo>
+    cd <repo>
+    git remote add -f origin <url>
+
+    git config core.sparseCheckout true
+
+    echo "some/dir/" >> .git/info/sparse-checkout
+    echo "another/sub/tree" >> .git/info/sparse-checkout
+
+From: https://askubuntu.com/questions/460885/how-to-clone-git-repository-only-some-directories#645276
+

contrib/modern-js-cheatsheet

@@ -0,0 +1,5 @@
+    git checkout -b rewritten-branch
+
+    git filter-branch --prune-empty --subdirectory-filter <folder_name> rewritten-branch
+
+From: https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/

contrib/moving_cli_by_clement_chastagnol_expanded_multi_os_2.png

@@ -0,0 +1,7 @@
+I have started thinking of blank lines as "separating/grouping concepts when needed".
+
+So if I have three concepts on three lines, I might put all three lines together, to save space.
+
+But if one of those concepts now suddenly needs two lines, I will put some blank lines around it, to separate it from the other concepts/tasks.
+
+Also, I will keep a line or two immediately next to an if block or for loop, if that line is part of the same task.

contrib/originals/moving_cli_blah.svg

@@ -0,0 +1,17 @@
+In the past we have stored `_id` and `id` fields in each document. This has been somewhat confusing!
+
+I think we did that because the mongo ObjectIds were considered too long and ugly for the front-end and for users.
+
+Instead of doing that again, if we don’t want to use ObjectIds, we have other options.
+
+We can actually set `_id` to anything we want, as long as it is unique!
+
+1. We can set `_id` to an incrementing number: 1, 2, 3, … This is good to look at, but not good for sharding. Only suitable for small collections which we don’t want to shard (< 10,000).
+
+2. We can set `_id` to a shorter random id like `J5m9g~0J`, e.g. using [nanoid](https://github.com/ai/nanoid) This is sharding-friendly, and we can use their collision probability [calculator](https://alex7kom.github.io/nano-nanoid-cc/) to select a length that is suitable for our collection.
+
+   (An alternative is [dylang/shortid](https://github.com/dylang/shortid) but nanoid appears to be better. There are [collision concerns](https://github.com/ai/nanoid/issues/8) and [prediction concerns](https://github.com/dylang/shortid/issues/70) with shortid.)
+
+   (We can use `-` instead of `~` if we prefer.  But either way, we should [avoid](https://github.com/dylang/shortid/issues/96) using nanoids that have one of those symbols at the end!  Probably simpler to just reduce the alphabet to alphanumerics.)
+
+By default, mongo uses ObjectId to generate long _ids because they are guaranteed to be unique even in the worst-case scenarios. But in situations when we know the number of documents created will be low we can opt for short _ids.

contrib/originals/moving_cli_by_clement_chastagnol.png

@@ -0,0 +1,19 @@
+# What we discovered about setState today
+
+When calling `this.setState()`, we should never refer to `this.state`.
+
+Why?  Because the state update we pass will be applied later, asynchronously.  By that time, `this.state` might have changed, but our update was based on the old copy of `this.state`!
+
+    // BAD
+    this.setState({ counter: this.state.counter + 1 })
+
+    // GOOD (can be safely applied asnchronously)
+    this.setState((previousState) => ({ counter: previousState.counter + 1 }))
+
+But, if you are just clobbering a property, without updating it or worrying about previous states, you can just do:
+
+    this.setState({ counter: 0 })
+
+Short read: https://medium.com/@wereHamster/beware-react-setstate-is-asynchronous-ce87ef1a9cf3
+
+Long read: https://medium.freecodecamp.org/functional-setstate-is-the-future-of-react-374f30401b6b

git/checkout_only_part_of_a_git_repo.md

@@ -0,0 +1,17 @@
+https://github.com/yannickcr/eslint-plugin-react/issues/491#issuecomment-196756317
+
+```js
+const foo = (a, b) => (
+  <View>
+    <BigComponent data={a} />
+    <BigComponent data={b} />
+  </View>
+)
+```
+
+You might think that foo will not be called if `a` and `b` remain the same.
+
+However [for reasons of performance]() this is not applied by default.
+
+But it looks like [you can apply it when you need it](https://github.com/facebook/react/issues/5677#issuecomment-241265146).
+

git/rewrite_branch_extracting_only_one_folder.md

@@ -0,0 +1,37 @@
+# React
+
+## this.setState() is asynchronous
+
+TLDR: Do not refer to `this.state` when calling `this.setState()`.  Pass a function to setState instead.
+
+It is fine to update state with a small merge:
+
+    this.setState({ foo: 2 })
+    this.setState({ bar: 7 })
+
+but if you need to refer to the current state, then be careful:
+
+    // Avoid this form
+    this.setState({ foo: this.state.foo * 2 })
+
+One change like this will work, but if you make two updates within one cycle, you may encounter problems.  Because setState does not apply your merges immediately.  It waits and applies them later.
+
+    // BAD
+    // The second and third calls will still be using the OLD state!
+    this.setState({ foo: this.state.foo * 4 })
+    this.setState({ foo: this.state.foo / 2 })
+    this.setState({ bar: this.state.foo + 5 })
+
+In the example above, the first change to foo gets completely discarded.  `this.state` will not change until some point in the future, when React decides to apply your state changes.
+
+In order to handle the asynchronous nature of setState, we can provide it with a function argument.  The function will accept the current state, and return a merge.
+
+    // GOOD
+    // All calls will be applied to the state in turn
+    this.setState(state => ({ foo: state.foo * 4 }))
+    this.setState(state => ({ foo: state.foo / 2 }))
+    this.setState(state => ({ bar: state.foo + 5 }))
+
+With a starting state of `{foo: 1}` we will end with state `{foo: 2, bar: 7}` as desired.
+
+

how_to_use_blank_lines_in_code.md

@@ -0,0 +1,5 @@
+Q: Should I store `foo` in the React Component’s state or in the Redux store?
+
+A: For global (shared) app state, ideally use the Redux store. For re-usable components, use the component’s own state. When in doubt, do whatever is less awkward.
+
+https://github.com/reactjs/redux/issues/1287#issuecomment-175351978

mongo/shorter_ids.txt

@@ -0,0 +1 @@
+https://github.com/galkinrost/redux-state

react/setState_is_asynchronous.md

@@ -0,0 +1,51 @@
+# Quick introduction
+
+Open a folder in Vim:
+
+    $ vim ./project
+
+Or if you already have Vim open:
+
+    :e ./project
+
+You can switch netrw to tree list view if you like:
+
+    iii
+
+Move down to a file you want to open and open it in a vertical split:
+
+    v
+
+Now if you want the file view on the left, you might want to swap the windows (panes):
+
+    CTRL-W x
+
+Now if you want to open another file, `v` would create another split, giving you three windows (panes).  That's probably not what you want.
+
+So to open another file in the same ("previous") window, hover over the file and hit:
+
+    P
+
+You can expand or shrink the current window with:
+
+    30 CTRL-W >
+
+    5 CTRL-W <
+
+
+# Configuration
+
+I use the following defaults in my `.vimrc`:
+
+    " Default to tree view
+
+    let g:netrw_liststyle = 3
+
+    " Make `v` open the file on the right rather than the left
+
+    let g:netrw_altv = 1
+
+    " Make the split use more space for editor than for tree
+
+    let g:netrw_winsize = 80
+

react/stateless_render_functions_are_not_memoized.md

@@ -0,0 +1 @@
+Cmd-Shift-8 (*)        Toggle column select mode