jefffriesen

/* eslint strict: 0 */
'use strict';
const webpack = require('webpack')
const path = require('path')


// Attempt at getting deck.gl working with webpack. See https://github.com/uber/deck.gl/issues/247
// This works for react-map-gl but not deck.gl.
module.exports = {
  module: {

jefffriesen

// Place your key bindings in this file to overwrite the defaults
[
  {
    "key": "ctrl+v c",
    "command": "calva.connect"
  },
  {
    "key": "ctrl+alt+v c",
    "command": "-calva.connect"
  },

jefffriesen

height: 600
license: MIT

jefffriesen

Our Code Style

Function programming is a collection of approaches and tools. We aren't dogmatic about using all of them. For Javascript, we don't use these often:

• Currying
• Functors
• Function composition
• Recursion

We definitely use these a lot:

• Higher order functions
• Pure functions

jefffriesen

Keybase proof

I hereby claim:

• I am jefffriesen on github.
• I am jefffriesen (https://keybase.io/jefffriesen) on keybase.
• I have a public key ASBgWtmXo3PHrqlt83GAVIzPL4ah-4jJN-zms7rxAKqxtAo

To claim this, I am signing this object:

jefffriesen

1. Start with a verb
2. Make ticket actionable. Title should complete the phrase “This ticket will….” (which means it starts with a verb). They need to have a closable finished state. “Make it better” isn’t actionable.
3. Make small, specific tickets. If needed you can break it out into subtasks

Examples: Good: “Prevent Nav Bar From Bouncing on Scroll” Bad: “Navigation is Wonky”

Good: “Implement Home Page Right Rail Promo Block” Bad: “Homepage updates”

jefffriesen

  // Available variables:
  // - Machine
  // - interpret
  // - assign
  // - send
  // - sendParent
  // - spawn
  // - raise
  // - actions

jefffriesen

This is a d3.js visualization of US zip codes.

Original zip code dataset from Geocommons.

5MB shapefile with properties such as zipcode, state, name, population, area, more.

http://geocommons.com/overlays/54893 (Thank you Bill Greer)

This converts it nicely: