Jeremy Battle battlejj

External Resources

linuxacademy.com (Training)
Acloud.guru (training)
Read the top-level Documentation and FAQs for all the major AWS resources (EC2, S3, RDS, Auto Scaling, etc). The answers to the "nit-picky" questions can be found here. It's also helpful to go deeper on VPCs and networking-related concepts.
- VPC http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html
- VPC Security http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Security.html
- VPC Route Tables http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Route_Tables.html
Everyone says read the white papers. The ones I read were:
- Security Best Practices https://d0.awsstatic.com/whitepapers/Security/AWS_Security_Best_Practices.pdf
Cloud Best Practices https://d0.awsstatic.com/whitepapers/AWS_Cloud_Best_Practices.pdf

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

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc

	import * as React from 'react';
	import {
	Field as FormField,
	InjectedFormProps,
	reduxForm,
	} from 'redux-form';

	interface CustomProps {
	customText: string;
	}

	import { expect } from 'chai';
	import superagent from 'superagent';
	import mockSuperagent from 'superagent-mock';
	import * as Errors from '../../../common/utils/errors';

	// Under test.
	import login from './login';

	describe(`login api`), () => {
	const serverEndPoint = `http://foobar.com/login`;

	import { inspect } from 'util';
	import {
	graphql,
	GraphQLEnumType,
	GraphQLID,
	GraphQLInterfaceType,
	GraphQLObjectType,
	GraphQLList,
	GraphQLNonNull,
	GraphQLSchema,

	.
	├── actions
	├── stores
	├── views
	│ ├── Anonymous
	│ │ ├── __tests__
	│ │ ├── views
	│ │ │ ├── Home
	│ │ │ │ ├── __tests__
	│ │ │ │ └── Handler.js

	#!/usr/bin/env python2
	"""
	Author: takeshix <[email protected]>
	PoC code for CVE-2014-0160. Original PoC by Jared Stafford ([email protected]).

	Supportes all versions of TLS and has STARTTLS support for SMTP,POP3,IMAP,FTP and XMPP.
	"""

	import sys,struct,socket
	from argparse import ArgumentParser

	var Promise = require('es6-promise').Promise;

	// idea borrowed from Q.spread
	Promise.prototype.spread = function(fn) {
	return this.then(function() {
	if (!arguments \|\| arguments.length === 0) {
	return fn.apply();
	}
	return fn.apply(null, arguments[0]);
	});