-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
800 lines (710 loc) · 30.1 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Beyond the Fat Arrow - Functional Programming in Javascript</title>
<meta name="author" content="Ben Glassman">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.4.0/css/font-awesome.min.css">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/black.css" id="theme">
<!-- Code syntax highlighting -->
<link rel="stylesheet" href="lib/css/zenburn.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<style>
strong, .highlight { color: #42affa; }
.lowlight { opacity: 0.5; }
.intro body::after {
content: '';
background-image: url(img/arrow-dog.jpg);
background-size: contain;
background-position: center center;
opacity: 0.08;
position: absolute;
top: 0;
left: 0;
z-index: -1;
height: 100vh;
width: 100%;
}
.intro .present, .intro .present * {
text-shadow: 2px 2px 2px rgba(0, 0, 0, 0.75);
}
.use-right-now body::after {
content: '';
background-image: url(img/electronic-superhighway.jpg);
background-repeat: no-repeat;
background-position: 50% 0;
background-size: auto 100%;
opacity: 0.50;
position: absolute;
top: 0;
left: 0;
z-index: -1;
height: 100vh;
width: 100%;
}
ul, li { list-style: none; }
li::before {
list-style: none;
font-family: FontAwesome;
color: #42affa;
opacity: 0.25;
content: '\f061';
display: inline-block;
margin-right: 0.25em;
}
.reveal .slides section .fragment.visible { opacity: 0.35; }
.reveal .slides section .current-fragment.visible { color: #fff; opacity: 1; }
.reveal .question-box { position: relative; }
.reveal .question-text { font-size: 150%; }
.reveal .question-mark {
position: absolute;
text-align: center;
opacity: 0.05;
font-size: 600%;
color: #fff;
top: -0.2em;
left: 0;
z-index: -1;
width: 100%;
line-height: 1em;
}
.reveal section img { border: 0; background: none; box-shadow: none; }
.reveal .babel-logo {
background: #f5da55;
}
.reveal .twocol {
position: relative;
overflow: hidden;
}
.reveal .twocol > * {
float: left;
width: 45%;
margin-right: 10%;
}
.reveal .twocol > *:last-child { margin-right: 0; }
.twocol::after {
font-family: FontAwesome;
content: "\f061";
opacity: 0.2;
color: #fff;
position: absolute;
top: 50%;
left: 50%;
transform: translateX(-50%) translateY(-50%);
-webkit-transform: translateX(-50%) translateY(-50%);
}
.reveal small {
vertical-align: middle;
}
.hl1 { color: #FA7921; }
.hl2 { color: #9BC53D; }
.pipes body::after {
content: '';
background-image: url(img/thepoint-pipes.jpg);
background-size: contain;
background-position: center center;
opacity: 0.4;
position: absolute;
top: 0;
left: 0;
z-index: -1;
height: 100vh;
width: 100%;
}
</style>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body>
<div class="reveal">
<div class="slides">
<section data-state="intro">
<h1>Beyond <br /><small>the</small> Fat Arrow</h1>
<h3>Functional Programming <small>in</small> Javascript</h3>
<div style="text-align: right; padding-top: 1em;">
<h4 style="margin-bottom: 0">Ben Glassman</h4>
<p style="margin: 0;">
<small>
Email <span class="lowlight">@</span> <a href="mailto:ben@vtdesignworks.com" target="_blank">ben@vtdesignworks.com</a><br />
Director of Development <span class="lowlight">@</span> <a href="http://vtdesignworks.com" target="_blank">Vermont Design Works</a><br />
Adjunct Professor <span class="lowlight">@</span> <a href="http://champlain.edu" target="_blank">Champlain College</a><br />
</small>
</p>
<p style="font-size: 50%;">Interested in writing apps in React with ES6?<br />
<strong>We are hiring</strong> front-end and back-end devs!</p>
</div>
</section>
<section>
<h2>Why <strong>Functional</strong> Programming?</h2>
<blockquote>
<p>“Write <del>programs</del> functions that do one thing and do it well. Write <del>programs</del> functions to work together.”</p>
<p>– Doug McIlroy, inventor of UNIX pipes</p>
</blockquote>
</section>
<section>
<h2>Why <strong>Functional</strong> Programming?</h2>
<ul>
<li>Smaller units of code are....</li>
<li class="fragment">...easier to understand</li>
<li class="fragment">...easier to test</li>
<li class="fragment">...easier to re-use</li>
<li class="fragment">...easier to refactor</li>
</ul>
</section>
<section>
<h2 class="question-box">
<span class="question-text">
Great,<br />
<small>but</small> <strong>How</strong>
</span>
<span class="question-mark">?</span>
</h2>
</section>
<section>
<p>To achieve our goal, we need to do 2 things:</p>
<ol>
<li><strong class="hl1">Break</strong> our program into small units</li>
<li><strong class="hl2">Combine</strong> these units into larger ones</li>
</ol>
<p>This talk looks at techniques for<br />
<strong class="hl1">decomposition</strong> and <strong class="hl2">composition</strong>.</p>
</section>
<section>
<p>How do we make this function more re-usable?</p>
<pre><code data-trim contenteditable class="javascript">
var characters = [
{id: 1, name: 'Arrow'},
{id: 2, name: 'Oblio'},
];
var characterIds = characters.map(function(character) {
return character.id;
});
</code></pre>
</section>
<section>
<p>Step 1: Parameterize the Property Name</p>
<pre><code data-trim contenteditable class="javascript">
function get(propName, object) {
return object[propName];
}
var characters = [
{id: 1, name: 'Arrow'},
{id: 2, name: 'Oblio'},
];
var characterIds = characters.map(get); // ?!@#
</code></pre>
<p class="fragment">That was pointless!</p>
</section>
<section>
<p>Step 2: Make it Fit the Desired Interface</p>
<pre><code data-trim contenteditable class="javascript">
function get(propName, object) {
return object[propName];
}
function getId(object) {
return get('id', object);
}
var characters = [
{id: 1, name: 'Arrow'},
{id: 2, name: 'Oblio'},
];
var characterIds = characters.map(getId);
</code></pre>
<p class="fragment">Manual and quite ugly.<br />
Wouldn't it be nice if we had a way to easily<br />transform get into getId?</p>
</section>
<section>
<h2>First-class Functions</h2>
<h3>Functions as Values</h3>
<p>A programming language has <strong>first-class functions</strong> if...</p>
<ul>
<li>Functions can be passed as arguments</li>
<li>Functions can return functions as their return values</li>
<li>Functions can be assigned to variables</li>
</ul>
</section>
<section>
<h2>First-class Function Examples</h2>
<ul class="fragment">
<li>Array.map/sort/filter</li>
<li>Promise.then</li>
<li>addEventListener</li>
</ul>
</section>
<section>
<p>Step 3: Make get return a function</p>
<pre><code data-trim contenteditable class="javascript">
function get(propName) {
return function(object) {
return object[propName];
};
}
var characters = [
{id: 1, name: 'Arrow'},
{id: 2, name: 'Oblio'},
];
var characterIds = characters.map(get('id'));
</code></pre>
<p class="fragment">Better, but writing nested functions is tedious...</p>
</section>
<section>
<p>What is the Relationship between these 2 functions?</p>
<pre><code data-trim contenteditable class="javascript">
function getA(propName, object) {
return object[propName];
}
function getB(propName) {
return function(object) {
return object[propName];
};
}
</code></pre>
<p class="fragment">getB takes getA's first argument (propName) and returns a function that takes getA's second argument (object) and returns getA(propName, object)</p>
</section>
<section>
<p>Can we write a function to turn getA into getB?</p>
<pre><code data-trim contenteditable class="javascript">
function getA(propName, object) {
return object[propName];
}
function ???(getA, arg1) {
return function(arg2) {
return getA(arg1, arg2);
};
}
</code></pre>
<p class="fragment">What do we call it?</p>
</section>
<section>
<h2>Left Apply</h2>
<p><strong>Partial Application</strong>: Application is calling a function with arguments, partial refers to the fact that we dont have all the arguments yet</p>
<pre><code data-trim contenteditable class="javascript">
function get(propName, object) {
return object[propName];
}
function leftApply(fn, arg1) {
return function(arg2) {
return fn(arg1, arg2);
};
}
const getId = leftApply(get, 'id');
characters.map(getId);
</code></pre>
</section>
<section>
<h2>There is Another Name...</h2>
<p>Javascript supports partial application natively.</p>
<pre><code data-trim contenteditable class="javascript">
function get(propName, object) {
return object[propName];
}
const getId = get.bind(null, 'id');
characters.map(getId);
</code></pre>
</section>
<section>
<h2>Partial Application</h2>
<p>Allows us to write our function normally (immediately evaluating) and have the returning of nested functions handled automatically.</p>
<p>leftApply (and its corollary rightApply) helps us to decompose a function into a simpler function by supplying one of its arguments up front.</p>
</section>
<section>
<h2>Higher Order Functions</h2>
<p>Left apply is an example of a higher order function.</p>
<p>Higher Order functions are functions which accept a function as an argument OR return a function as a value.</p>
<p>We can write higher order functions to transform other functions.</p>
</section>
<section>
<h2>Which is more Readable?</h2>
<pre><code data-trim contenteditable class="javascript">
characters.map(leftApply(get, 'id'));
characters.map(get('id'));
</code></pre>
</section>
<section>
<h2>Currying</h2>
<p>A technique which turns a function of <strong>arity</strong> X of into a nested series of X <strong>unary</strong> (single argument) functions.</p>
<pre><code data-trim contenteditable class="javascript">
var character = { id: 5, name: 'Rock Man' };
get('name', character); // 'Rock Man'
var curriedGet = curry(get);
curriedGet('name')(character); // 'Rock Man'
var getName = curriedGet('name');
getName(character); // 'Rock Man'
</code></pre>
<p>Anybody know why its called currying?</p>
</section>
<section>
<p>Our get function from earlier was a curried function:</p>
<pre><code data-trim contenteditable class="javascript">
function get(propName, obj) {
return obj[propName];
}
function curriedGet(propName) {
return function(obj) {
return obj[propName];
};
}
</code></pre>
<p>Curried functions accept 1 argument at a time. You call the returned function with the next argument, etc. When the final argument is supplied, the function is called and the value is returned.</p>
</section>
<section>
<p>Final Get Function</p>
<pre><code data-trim contenteditable class="javascript">
const get = curry(function get(propName, obj) {
return obj[propName];
});
var characters = [
{id: 3, name: 'The Count'},
{id: 4, name: 'The Pointed Man'},
];
var characterIds = characters.map(get('id'));
</code></pre>
</section>
<section>
<p>Take it Further: Curried Map</p>
<pre><code data-trim contenteditable class="javascript">
const get = curry(function get(propName, obj) {
return obj[propName];
});
const map = curry(function map(fn, mappable) {
return mappable.map(fn);
});
var characters = [
{id: 3, name: 'The Count'},
{id: 4, name: 'The Pointed Man'},
];
const getIds = map(get('id'));
var characterIds = getIds(characters);
</code></pre>
</section>
<section>
<h2>Functions <small>as</small> Values</h2>
<p>Its not just passing functions as args or storing them in vars.</p>
<p>We can use functions that create new functions by <strong class="hl1">breaking down</strong> existing functions, like leftApply or curry.</p>
<p>We can also use functions that create new functions by <strong class="hl2">combining</strong> existing functions.</p>
<p>This makes sense when we think of functions as values in the same way as we think of numbers or strings as values. We can perform operations on them to combine or transform them and create new values.</p>
</section>
<section data-state="pipes">
<h2>What Makes the *NIX command line so powerful?</h2>
<div style="height: 400px"></div>
</section>
<section>
<h2>What Makes the *NIX command line so powerful?</h2>
<pre><code data-trim contenteditable class="shell">
# Edit the result of a command in vim
du -h /var | sort -hr | head -10 | vim -
# Create a file and edit it
touch myfile.txt && vim $_
# Open modified files in vim
vim $(git status -uno --porcelain | awk '{ print $2 }')
</code></pre>
</section>
<section>
<h2>What Makes the *NIX command line so powerful?</h2>
<ul>
<li class="fragment"><strong>Uniform Interface</strong>: Take a single input and return a single output</li>
<li class="fragment"><strong>Composable</strong>: Pipes make it easy to chain commands together by passing the output of one into the input of the next.</li>
<li class="fragment"><strong>Lazy</strong>: We can provide some args/options up front to the each command without executing it until the input is provided</li>
</ul>
</section>
<section>
<h2>Adding logging to a function:<br />Manual Implementation</h2>
<pre><code data-trim contenteditable class="javascript">
function logBeforeAdd(x, y) {
console.log(x, y);
return add(x, y);
}
</code></pre>
</section>
<section>
<h2>Adding logging to a function:<br />Higher Order Function</h2>
<pre><code data-trim contenteditable class="javascript">
function logBefore(fn) {
return function() {
console.log(arguments);
return fn.apply(this, arguments);
};
}
</code></pre>
<p class="fragment">What is the behavior of the logBefore fn?</p>
</section>
<section>
<h2>Adding logging to a function:<br />Decorator</h2>
<p>A <strong>decorator</strong> is a higher order function that takes one function as its argument and returns a new function that is closely related to the original function</p>
<pre><code data-trim contenteditable class="javascript">
function logBefore(fn) {
return function() {
console.log(arguments);
return fn.apply(this, arguments);
}
}
</code></pre>
<p class="fragment">Side-effect made explicit & isolated</p>
</section>
<section>
<h2>Retry Decorator</h2>
<pre><code data-trim contenteditable class="javascript">
function retry(fn, maxTries) {
return function() {
var error;
while (maxTries--) {
try {
return fn.apply(this, arguments);
} catch (err) {
error = err;
}
}
throw error;
};
}
const resilientLoadUsers = retry(loadUsers, 3);
const users = resilientLoadUsers();
</code></pre>
</section>
<section>
<h2>Memoize (Caching) Decorator</h2>
<pre><code data-trim contenteditable class="javascript">
function memoize(fn) {
var memos = {};
return function() {
var key = JSON.stringify(Array.from(arguments));
if (!memos.hasOwnProperty(key)) {
console.log('cache miss on: '+key);
memos[key] = fn.apply(this, arguments);
} else {
console.log('cache hit on: '+key);
}
return memos[key];
};
};
const memoizedAdd = memoize(add);
memoizedAdd(1, 2); // cache miss on: [1,2]
memoizedAdd(1, 2); // cache hit on: [1,2]
</code></pre>
</section>
<section>
<h2>More Decorators</h2>
<ul>
<li class="fragment">
<strong>flip</strong>: Reverse the function's argument order
</li>
<li class="fragment">
<strong>unary</strong>: Ignore all but first argument
</li>
<li class="fragment">
<strong>map</strong>: Calls the function on each element of an array
</li>
<li class="fragment">
<strong>maybe</strong>: Return null if any of its arguments are falsy.
</li>
<li class="fragment">
<a href="http://raganwald.com/2012/12/01/more-combinators.html">fluent</a>,
<a href="http://ramdajs.com/0.20.1/docs/#binary">binary</a>,
<a href="http://ramdajs.com/0.20.1/docs/#comparator">comparator</a>,
<a href="http://ramdajs.com/0.20.1/docs/#cond">cond</a>,
<a href="http://ramdajs.com/0.20.1/docs/#complement">complement</a>,
and many more
</li>
</ul>
</section>
<section>
<h2>Chaining Functions w/ Pipe</h2>
<p>Decouple complex multi-step operation into small, manageable chunks.</p>
<pre><code data-trim contenteditable class="javascript">
function uppercase(string) {
return string.toUpperCase();
}
function pipe() {
const functionQueue = Array.from(arguments);
return function() {
const initialValue = arguments[0];
return functionQueue.reduce(
(returnValue, fn) => return fn(returnValue),
initialValue
);
}
}
const getUppercaseName = pipe(get('name'), uppercase);
const uppercaseNames = characters.map(getUppercaseName);
</code></pre>
<p>compose = flip(pipe);</p>
</section>
<section>
<h2>Generalizing logBefore</h2>
<pre><code data-trim contenteditable class="javascript">
const log = console.log.bind(console);
function logBefore(fn) {
return function() {
log(arguments);
return fn.apply(this, arguments);
};
}
</code></pre>
<p>How do we make this more re-usable?</p>
</section>
<section>
<h2>Step 1: Parameterize the beforeFn</h2>
<pre><code data-trim contenteditable class="javascript">
const log = console.log.bind(console);
function before(beforeFn, mainFn) {
return function() {
beforeFn.apply(this, arguments);
return mainFn.apply(this, arguments);
};
}
const logBeforeAdd = before(log, add);
const logBeforeClick = before(log, handleClick);
</code></pre>
<p class="fragment">Can we make this even more re-usable?</p>
</section>
<section>
<h2>Step 2: Curried Before</h2>
<pre><code data-trim contenteditable class="javascript">
const log = console.log.bind(console);
const before = curry(function before(beforeFn, mainFn) {
return function() {
beforeFn.apply(this, arguments);
return fn.apply(this, arguments);
};
});
const logBefore = before(log);
const logBeforeAdd = logBefore(add);
const logBeforeClick = logBefore(handleClick);
</code></pre>
</section>
<section>
<h2><strong>before</strong> is a Combinator</h2>
<p>Combinators are functions that create more complex values by combining the provided arguments.</p>
<p>We're used to thinking about combining values likes numbers (addition), arrays (concat), or objects (Object.assign), but less so with functions.</p>
<p><strong>before(beforeFn, mainFn)</strong> is a function combinator, a higher order function that create more complex functions by combining other functions.</p>
</section>
<section>
<h2>Around Example</h2>
<p>Return the result of calling aroundFn with mainFn and all other arguments. You can implement many decorators using around.</p>
<pre><code data-trim contenteditable class="shell">
function around(wrapperFn, mainFn) {
return function() {
var args = [mainFn].concat(Array.from(arguments));
return wrapperFn.apply(this, args);
};
}
const addAndDouble = around(function(mainFn, ...args) {
return mainFn(...args) * 2;
}, add);
addAndDouble(1, 2); // 6
</code></pre>
</section>
<section>
<h2>Provided & Excepting Combinators</h2>
<ul>
<li>
<strong>provided(predicateFn, mainFn)</strong> predicateFn serves as a guard clause where returning falsy prevents mainFn from being called.
</li>
<li>
<strong>excepting(predicateFn, mainFn)</strong> Inverse of provided, returning truthy from predicateFn will result in an early return.
</li>
</ul>
</section>
<section>
<h2>Pre/Post Condition Combinators</h2>
<ul>
<li>
<strong>precondition(conditionFn, exception, mainFn)</strong> Call conditionFn before mainFn and throw exception if it returns false.
</li>
<li>
<strong>postcondition(conditionFn, exception, mainFn)</strong> Call conditionFn after mainFn and throw exception if it returns false.
</li>
</ul>
</section>
<section>
<h2>Uses</h2>
<ul>
<li>
<strong>Separator of Concerns</strong>: Separate cross-cutting concerns like caching, logging, authentication, authorization, etc. from application code
</li>
<li>
<strong>Lazy Loading</strong>: before/around can be used to lazily initialize data when it is asked for.
</li>
<li>
<strong>Enforcing Invariants</strong>: Pre/post condition combinators can be used to share code that enforces invariants
</li>
<li>
<strong>Side Effects</strong>: before/after can be used to attach side-effects to otherwise pure functions
</li>
<li>
<strong>Guard Clauses</strong>: Useful to create early returns from functions
</li>
</ul>
</section>
<section>
<h2>Summary</h2>
<ul>
<li>Smaller units of code make programs <strong>easier to understand</strong></li>
<li>Functional concepts apply to <strong>any language with first-class functions</strong></li>
<li>Declarative approach makes code <strong>more readable</strong></li>
<li>Expands vocabulary for <strong>describing & creating relationships between functions</strong></li>
</ul>
</section>
<section data-state="intro">
<h1>Beyond the Fat Arrow</h1>
<h3>
Thank You!<br />
<small>Matt, Everybody who showed up tonight</small>
</h3>
<div style="text-align: right; padding-top: 1em;">
<h4 style="margin-bottom: 0">Ben Glassman</h4>
<p style="margin: 0;">
<small>
Email <span class="lowlight">@</span> <a href="mailto:ben@vtdesignworks.com" target="_blank">ben@vtdesignworks.com</a><br />
Director of Development <span class="lowlight">@</span> <a href="http://vtdesignworks.com" target="_blank">Vermont Design Works</a><br />
Adjunct Professor <span class="lowlight">@</span> <a href="http://champlain.edu" target="_blank">Champlain College</a><br />
</small>
</p>
<p style="font-size: 50%;">Interested in writing apps in React with ES6?<br />
<strong>We are hiring</strong> front-end and back-end devs!</p>
</div>
</section>
<section>
<h2>Resources</h2>
<ul>
<li><a href="https://pragprog.com/magazines/2013-01/functional-programming-basics">Functional Programming Basics</a></li>
<li><a href="http://maryrosecook.com/blog/post/a-practical-introduction-to-functional-programming">Practice Introduction to Functional Programming</a></li>
<li><a href="http://bitemyapp.com/posts/2014-12-31-functional-education.html">Functional Education</a></li>
<li><a href="http://ramdajs.com/0.19.1/index.html">RamdaJS</a> & <a href="http://fr.umio.us/why-ramda/">Why Ramda</a></li>
<li><a href="https://www.npmjs.com/package/method-combinators">Method Combinators</a></li>
<li><a href="https://github.com/PuerkitoBio/advice">Advice</a></li>
<li><a href="https://speakerdeck.com/anguscroll/how-we-learned-to-stop-worrying-and-love-javascript">How we Learned to Stop Worrying and Love Javascript</a></li>
<li><a href="https://vimeo.com/153097877">Javascript Combinators</a></li>
</ul>
</section>
</div>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
Reveal.initialize({
controls: false,
progress: true,
history: true,
transition: 'fade',
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/highlight/highlight.js', async: true, condition: function() { return !!document.querySelector( 'pre code' ); }, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true }
]
});
</script>
</body>
</html>