One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
* { | |
-webkit-font-smoothing: antialiased; | |
-webkit-font-feature-settings: "liga" on, "calt" on; | |
} | |
atom-text-editor .cursor-line { | |
-webkit-font-feature-settings: "liga" off, "calt" off; | |
} |
""" | |
Minimal character-level Vanilla RNN model. Written by Andrej Karpathy (@karpathy) | |
BSD License | |
""" | |
import numpy as np | |
# data I/O | |
data = open('input.txt', 'r').read() # should be simple plain text file | |
chars = list(set(data)) | |
data_size, vocab_size = len(data), len(chars) |
daemon off; | |
# Heroku dynos have at least 4 cores. | |
worker_processes <%= ENV['NGINX_WORKERS'] || 4 %>; | |
events { | |
use epoll; | |
accept_mutex on; | |
worker_connections 1024; | |
} |
/** | |
* Basic proof of concept. | |
* - Hot reloadable | |
* - Stateless stores | |
* - Stores and action creators interoperable with Redux. | |
*/ | |
import React, { Component } from 'react'; | |
export default function dispatch(store, atom, action) { |
const flattenTco = ([first, ...rest], accumulator) => | |
(first === undefined) | |
? accumulator | |
: (Array.isArray(first)) | |
? flattenTco([...first, ...rest]) | |
: flattenTco(rest, accumulator.concat(first)) | |
const flatten = (n) => flattenTco(n, []); | |
console.log(flatten([[1,[2,[[3]]]],4,[5,[[[6]]]]])) |
TL;DR, ActiveRecord's timestamps macro creates :created_at and :updated_at but Ecto's timestamps creates :inserted_at and :updated_at. If you already have a database setup and now want to switch from ActiveRecord rails to Ecto Elixir, you'll no doubt run into the following error:
(1054): Unknown column 'a0.inserted_at' in 'field list'
You can resolve this by going into your model file and making the following edit:
# models/appointments.ex
defmodule Appointment do
.table-list-triage { | |
display: none; | |
} | |
.triage-mode .table-list-non-triage, .triage-mode .table-list-filters { | |
display: none; | |
} | |
.boxed-group-list>li.approved .btn-sm, .boxed-group-list>li.rejected .btn-sm { | |
display: none; | |
} | |
.repo-list .participation-graph.disabled { |
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't