Roberto Bonvallet rbonvall

Applied Functional Programming with Scala - Notes

1. Mastering Functions

A function is a mapping from one set, called a domain, to another set, called the codomain. A function associates every element in the domain with exactly one element in the codomain. In Scala, both domain and codomain are types.

val square : Int => Int = x => x * x

This document has moved!

It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.

Things that programmers don't know but should

(A book that I might eventually write!)

Gary Bernhardt

I imagine each of these chapters being about 2,000 words, making the whole book about the size of a small novel. For comparison, articles in large papers like the New York Times average about 1,200 words. Each topic gets whatever level of detail I can fit into that space. For simple topics, that's a lot of space: I can probably walk through a very basic, but working, implementation of the IP protocol.

Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the node-forward discussions repo

io.js - what you need to know

io is a fork of node v0.12 (the next stable version of node.js, currently unreleased)
io.js will be totally compatible with node.js
the people who created io.js are node core contributors who have different ideas on how to run the project
it is not a zero-sum game. many core contributors will help maintain both node.js and io.js

Copy nbflatten.py to somewhere on $PATH. Then, in the root of a git repository, run these commands:

echo "*.ipynb diff=ipynb" >> .gitattributes 
git config diff.ipynb.textconv nbflatten.py

When you change a notebook and run git diff, you'll see the diff of flattened, simplified notebooks, rather than the full JSON. This does lose some information (metadata, non-text output), but it makes it easier to see simple changes in the notebook.

This doesn't help with merging conflicting changes in notebooks. For that, see nbdiff.org.

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.

	$ curl --help
	Usage: curl [options...] <url>
	--abstract-unix-socket <path> Connect via abstract Unix domain socket
	--alt-svc <file name> Enable alt-svc with this cache file
	--anyauth Pick any authentication method
	-a, --append Append to target file when uploading
	--basic Use HTTP Basic Authentication
	--cacert <file> CA certificate to verify peer against
	--capath <dir> CA directory to verify peer against
	-E, --cert <certificate[:password]> Client certificate file and password

	object InstantInsanity extends App {

	// scalastyle:off

	def undefined[T]: T = ???
	def ⊥[T]: T = undefined

	trait R
	trait G
	trait B

	/**
	* Examples of writing mixed unit/property-based (ScalaCheck) tests.
	*
	* Includes tables and generators as well as 'traditional' tests.
	*
	* @see http://www.scalatest.org/user_guide/selecting_a_style
	* @see http://www.scalatest.org/user_guide/property_based_testing
	*/

	import org.scalatest._

	(Chapters marked with * are already written. This gets reorganized constantly
	and 10 or so written chapters that I'm on the fence about aren't listed.)

	Programmer Epistemology
	* Dispersed Cost vs. Reduced Cost
	* Verificationist Fallacy
	* Mistake Metastasis
	The Overton Window
	Epicycles All The Way Down
	The Hyperspace Gates Were Just There