IntegerUnderflow integer-underflow

Eric Elliott: Composing Software

1. An Introduction: Composing Software: An Introduction – JavaScript Scene – Medium
1. The Rise and Fall of Functional Programming: The Rise and Fall and Rise of Functional Programming (Composing Software)
1. Why Learn Functional Programming in JavaScript?: Why Learn Functional Programming in JavaScript? (Composing Software)
1. A Functional Programmer’s Introduction to JavScript: A Functional Programmer’s Introduction to JavaScript (Composing Software)
1. Higher Order Functions: [Higher Order Functions (Compos

Eric Elliott's "Composing Software" Series

A collection of links to the excellent "Composing Software" series of medium stories by Eric Elliott.

Edit: I see that each post in the series now has index, previous and next links. However, they don't follow a linear flow through all the articles with some pointing back to previous posts effectively locking you in a loop.

The Imposter's Handbook

This a collection of interesting links found in The Imposter's Handbook by Rob Conery.

Content:

Introduction
A Little History
The Tools
Customizing The Terminal

Download videos from egghead

Install the React Developer Tools Chrome Extension.
Go to the egghead website, i.e. Getting Started with Redux
Click View -> Developer -> Javascript Console, then the React tab, then the <NextUpLessonList ...> tag.
Click back to the Console tab, then run:

Chapter 1 - Object Oriented Design

The purpose of design is to allow you to do design later, and it's primary goal is to reduce the cost of change.

SOLID Design:

Single Responsibility Principle: a class should have only a single responsibility
Open-Closed Principle: Software entities should be open for extension, but closed for modification (inherit instead of modifying existing classes).
Liskov Substitution: Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.
Interface Segregation: Many client-specific interfaces are better than one general-purpose interface.

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

	# Original Rails controller and action
	class EmployeesController < ApplicationController
	def create
	@employee = Employee.new(employee_params)

	if @employee.save
	redirect_to @employee, notice: "Employee #{@employee.name} created"
	else
	render :new
	end