1. el nino (l) vs xisco (w)
2. yarko (l) vs nasty ray (w)
3. scumbag jole (l) vs wing (w)
4. illz (l) vs cheerito (w)
5. pocket (l) vs kid colombia (w)
6. ronnie (l) vs hong 10 (w)
7. gun (l) vs kareem (w)
8. ken fury (l) vs gravity (w)
9. luigi (l) vs menno (w)
10. robin (l) vs issei (w)

A concise and tactical guide to learn to code.

Learning to code is hard. Many people are trying to learn to code, and many of them are frustrated with their progress not matching their expectations. Developer bootcamps have emerged to monetize this frustration.

The GUI is the most common UI by far. However, GUIs are expensive to create and iterate and frequently frustrating for the end user. These shortcomings could be addressed with better engineers and better product sense, but many companies can't afford or can't retain quality engineers, designers, et al. Does the GUI have too much marketshare? Are there other interfaces which are more useful?

Reasons why CLI is a great interface:

• All unix philosophy benefits, especially composibility, which implies network effects since CLIs' collective usefulness is an exponential or factorial function of the number of CLI tools available. You can pipe, grep, tail, curl any of your CLI outputs with any other CLI. (~50% of the benefit)

This is what I used to have:

(defn static-data []
  (for [row (range 10)]
    {:a "some" :b "fake" :c "data"}))

(def app-state (atom {:items (static-data)}))

;;; components

I just came across this interesting bit of javascript, which I've paraphrased:

var _ = require('underscore');
var coll = require('./some/external/array');

function contains(str, key) {
  return ~str.indexOf(key);
}