kevinmarks/gist:f74137c9c5ceb55c173134a8ac7563fc

## gistfile1.txt
#nodevember  @leeb: is going to give us a talk on how we think about architecture, not just code. "Architecture is a metaphor"
#nodevember  @leeb: Architecture originates from studying the arch, an infinitely composable shape that allows us to build amazing things.
#nodevember  @leeb: Pollios tells us architecture has: 1) Firmitas - durability 2) Utilitas - Suitable for purposes 3) Venustas - beauty
#nodevember  @leeb: Architecture is about making fundamental structural choices. In software, we choose the elements of abstraction.
#nodevember  @leeb: The problem of software architecture is trying to figure out what changed. So we try to add things that...change more?
#nodevember  @leeb: When models and views have to listen to each other, there is cascading problems and syncing.
#nodevember  @leeb: While REST helped us model our data in terms of a network service, it fails when we rely on other data.
#nodevember  @leeb: If we tightly control what can change in the first place, immutability gives us new principles.
#nodevember  @leeb: When he says principles, I hear promises. Principles allow us to rely on the validity of data.
#nodevember  @leeb: Immutable app architecture is derived from functional reactive programming, like Elm.
#nodevember  @leeb: Immutable means embracing the principle tightly controlling the changes that occur.
#nodevember  @leeb: Princple 1: Views. We use views to build a view tree. Create elements, change properties, refer to other elements. Slow!
#nodevember  @leeb: 2) Components are a pure function that transmutes the state of the world into a representation.
#nodevember  @leeb: We want to diff the virtual views to only send down the changed elements, not everything.
#nodevember  @leeb: Components render data from models.  Changed data has to be informed of what the application needs.
#nodevember  @leeb: GraphQL love fest. I've seen several of these warm fuzzies this year.
#nodevember  @: This is what I get for being late. I. missed the speaker intro. This talk is a study of taking Walmart to Node and React.
	#nodevember @leeb: is going to give us a talk on how we think about architecture, not just code. "Architecture is a metaphor"
	#nodevember @leeb: Architecture originates from studying the arch, an infinitely composable shape that allows us to build amazing things.
	#nodevember @leeb: Pollios tells us architecture has: 1) Firmitas - durability 2) Utilitas - Suitable for purposes 3) Venustas - beauty
	#nodevember @leeb: Architecture is about making fundamental structural choices. In software, we choose the elements of abstraction.
	#nodevember @leeb: The problem of software architecture is trying to figure out what changed. So we try to add things that...change more?
	#nodevember @leeb: When models and views have to listen to each other, there is cascading problems and syncing.
	#nodevember @leeb: While REST helped us model our data in terms of a network service, it fails when we rely on other data.
	#nodevember @leeb: If we tightly control what can change in the first place, immutability gives us new principles.
	#nodevember @leeb: When he says principles, I hear promises. Principles allow us to rely on the validity of data.
	#nodevember @leeb: Immutable app architecture is derived from functional reactive programming, like Elm.
	#nodevember @leeb: Immutable means embracing the principle tightly controlling the changes that occur.
	#nodevember @leeb: Princple 1: Views. We use views to build a view tree. Create elements, change properties, refer to other elements. Slow!
	#nodevember @leeb: 2) Components are a pure function that transmutes the state of the world into a representation.
	#nodevember @leeb: We want to diff the virtual views to only send down the changed elements, not everything.
	#nodevember @leeb: Components render data from models. Changed data has to be informed of what the application needs.
	#nodevember @leeb: GraphQL love fest. I've seen several of these warm fuzzies this year.
	#nodevember @: This is what I get for being late. I. missed the speaker intro. This talk is a study of taking Walmart to Node and React.