Julio Cesar pazthor

Fecha: [fecha]

Entre nosotros [nuestra empresa] y ustedes [nombre del cliente]

Compromiso:

Nuestro compromiso es hacer siempre lo mejor para satisfacer las necesidades y cubrir las expectativas de nuestros clientes, y es importante que ambas partes tengamos las cosas claras y por escrito de manera que todos entendamos qué es qué, quién debe hacer qué, cuándo debe hacerlo, y qué va a pasar si algo no sale como se planeó. Este convenio es muy sencillo y no encontrarán en él complicados términos legales o largos párrafos difíciles de entender. Buscamos lo mejor para ambas partes, ahora y en el futuro.

Antecedentes:

Scala's "type T in class C as seen from a prefix type S" with examples

Introduction

Recently, I found myself in need to precisely understand Scala's core typechecking rules. I was particulary interested in understanding rules responsible for typechecking signatures of members defined in classes (and all types derived from them). Scala Language Specification (SLS) contains definition of the rules but lacks any examples. The definition of the rules uses mutual recursion and nested switch-like constructs that make it hard to follow. I've written down examples together with explanation how specific set of rules (grouped thematically) is applied. These notes helped me gain confidence that I fully understand Scala's core typechecking algorithm.

As Seen From

Let's quote the Scala spec for As Seen From (ASF) rules numbered for an easier reference:

Gist

This is a quick tutorial explaining how to get a static website hosted on Heroku.

Why do this?

Heroku hosts apps on the internet, not static websites. To get it to run your static portfolio, personal blog, etc., you need to trick Heroku into thinking your website is a PHP app. This 6-step tutorial will teach you how.

Basic Assumptions

##Reactive System Design Links

#Articles and Papers

The Reactive Manifesto: http://www.reactivemanifesto.org/
https://en.wikipedia.org/wiki/Reactive_programming
https://en.wikipedia.org/wiki/Functional_reactive_programming
Design Methods for Reactive Systems book slides: http://booksite.elsevier.com/9781558607552/slides/slides.pdf
Programming without a callstack Event Driven Architectures By G Hohpe: http://www.eaipatterns.com/docs/EDA.pdf
On Distributed Memory Systems: http://blog.paralleluniverse.co/2012/07/10/on-distributed-memory/
Disruptor source code, papers and articles: https://lmax-exchange.github.io/disruptor/

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.

N.B. to run his examples in emacs, you'll want these aliases:

(defalias 'plus #'+)
(defalias 'quotient #'/)
(defalias 'times #'*)
(defalias 'difference #'-)

Lisp: Atoms and Lists

Carl Hewitt on Actors

Actor - Fundamental unit of computation, a computation model - not just a form of concurrency

An Actor has three essential elements:

1 - Processing - you have to get something done
2 - Storage - you have to be able to remember things
3 - Communication

Linux fun-o-matic

How to have some fun using the terminal.

Install cowsay [0] via : sudo apt-get install cowsay
Install fortune [1] via : sudo apt-get install fortune
Make sure you have Ruby installed via : ruby -v
Install the lolcat [2] via : gem gem install lolcat
Profit!

	# Compiled source #
	###################
	*.com
	*.class
	*.dll
	*.exe
	*.o
	*.so

	# Packages #

	*.aux
	*.glo
	*.idx
	*.log
	*.toc
	*.ist
	*.acn
	*.acr
	*.alg
	*.bbl