markalfred

echo "===> Installing xcode developer tools..."
xcode-select --install

echo "===> Generating new SSH key..."
echo ""
echo "Enter your email:"
read email
ssh-keygen -t rsa -b 4096 -C $email

eval "$(ssh-agent -s)"

markalfred

Yeah, the "container vs component" distinction is falling more and more out of favor with me. It's an okay pattern to start, but it's a pretty hard black/white in a place where things are a lot more grey.

In my opinion, there's no reason for this:

// app/index.jsx
import AppComponent from './App'

const AppContainer = ({foo, bar, baz, buz, wham, bam, alakazam, setFoo, setBar, setBaz, setBuz, setWham, setBam, setAlakazam}) =>
  <AppComponent foo={foo} bar={bar} baz={baz} buz={buz} wham={wham} bam={bam} alakazam={alakazam} setFoo={setFoo}, setBar={setBar}, setBaz={setBaz}, setBuz={setBuz}, setWham={setWham}, setBam={setBam}, setAlakazam={setAlakazam} />

markalfred

The trouble with ES6 named import/exports

-or-

Regarding renaming SET_RELATIONSHIP_INFORMATION_ERRORS to SET_ERRORS:

I've noticed a particular issue that seems to have come about with the advent of named import/exports in ES6 — that is, that variable names have grown in length by orders of magnitude. This seems to be the result of the need to namespace. For instance, let's say you have a set of user actions...

// user-actions.js

markalfred

#!/bin/sh

# Alot of these configs have been taken from the various places
# on the web, most from here
# https://github.com/mathiasbynens/dotfiles/blob/master/.osx

# Set the colours you can use
black='\033[0;30m'
white='\033[0;37m'
red='\033[0;31m'

markalfred

$.ajax('http://ethereumwisdom.com/data/chart/kraken_USD_1800.json?&rand=0.38954108371399343').then(function(data){var high = data.map(function(c) {return parseFloat(c.h)}).sort(function (a, b) { return a-b; }).reverse()[0]; var current = data[data.length-1].c; console.log('current:', current, 'high:', high)})

markalfred

def determine_output_pane(self):
  """
  When the user performs some action which results in a file being
  opened or generated in a new tab, we should place that "output"
  code in an adjacent pane. This method will determine the correct
  pane to place the output in. 

  It will use a tab to the right, if one exists in the current row.
  If not, output is placed in the adjacent tab to the left. Output
  should always be adjacent, and should never be on a different row,

markalfred

# Find the longest words you can type, alternating hands at each character. Y and B excluded.

egrep "^[$right]?([$left][$right]){6,}[$left]?\$" /usr/share/dict/words

# Qwerty
left=qwertasdfgzxcv
right=uiophjklnm

# Colemak
left=qwfpgarstdzxcv

markalfred

<snippet>
  <content><![CDATA[
Given(/^${1:Something called}${2: "(.*?)"}${3: does something}\$/) do |${4:variable_name}|
  ${0:}
end
]]></content>
  <!-- Optional: Set a tabTrigger to define how to trigger the snippet -->
  <tabTrigger>given-variable step</tabTrigger>
  <!-- Optional: Set a scope to limit where the snippet will trigger -->
  <!-- <scope>source.python</scope> -->