Jared M. Smith absynce

The Summarized Pragmatic Programmer

When I first started reading The Pragmatic Programmer, I summarized every chapter after I read it. I eventually stopped summarizing and just finished reading the book, but I intend on finishing the job. Writing the summaries greatly improved my comprehension of each chapter.

Chapters

[A Pragmatic Philosophy][1]
[A Pragmatic Approach][2]
[The Basic Tools][3]
[Pragmatic Paranoia][4]

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

Towards Discussion Guidelines

I personally like to have discussions in the spirit of the Socratic method. Instead of declaring my opinion, I ask a relevant question. How about this situation? What about this case? This has two possible outcomes.

The other person explains to me how things work in that case. I realize that I misunderstood, and we both come out enriched and in agreement.
The other person realizes that those situations are not covered. They realize they misunderstood, and we both come out enriched and in agreement.

In both cases, it could have been a conflict, egos crashing together. But by asking questions, it becomes a collaboration to find the best answer. Even the simple act of asking a question in the first place says, "I care what you have to say, we can agree on this." That said, I have noticed that it is definitely still possible for things to go wrong within this framework. How can this happen?

There was a passage from [The

Installing zsh – the easy way

The Z shell (zsh) is a Unix shell [...]. Zsh can be thought of as an extended Bourne shell with a large number of improvements, including some features of bash, ksh, and tcsh.

– Z shell – Wikipedia

Read more about ZSH at An Introduction to the Z Shell.

Choose one of the following options.

Learning FP the hard way: Experiences on the Elm language

by Ossi Hanhinen, @ohanhi

with the support of Futurice 💚.

Licensed under CC BY 4.0.

Editorial note

Requirements

no upfront installation/agents on remote/slave machines - ssh should be enough
application components should use third-party software, e.g. HDFS, Spark's cluster, deployed separately
configuration templating
environment requires/asserts, i.e. we need a JVM in a given version before doing deployment
deployment process run from Jenkins

	//based on the source of http://g.raphaeljs.com/linechart.html

	var options = {
	axis: "0 0 1 1", // Where to put the labels (trbl)
	axisxstep: 16 // How many x interval labels to render (axisystep does the same for the y axis)
	};

	document.addEventListener('DOMContentLoaded', function () {

	// Make the raphael object

	@ECHO OFF
	REM -- Automates cygwin installation

	SETLOCAL

	REM -- Change to the directory of the executing batch file
	CD %~dp0

	REM -- Configure our paths
	SET SITE=http://mirrors.kernel.org/sourceware/cygwin/

	using log4net;
	using NUnit.Framework;
	using Raven.Abstractions.Data;
	using Raven.Client;
	using Raven.Client.Document;
	using Raven.Client.Embedded;
	using Raven.Client.Indexes;
	using Raven.Client.Listeners;

	namespace RavenTesting

	import select
	import datetime

	import psycopg2
	import psycopg2.extensions

	from sqlalchemy import create_engine, text

	engine = create_engine("postgresql+psycopg2://vagrant@/postgres")