I'll be talking about functional programming from the point of view of a non-mathematically inclined programmer. I'll leave out talk of functors, monads, and category theory and instead focus on some practical functional programming that you can start using straight away. We'll start with `filter`, `map`, and `reduce`, before moving onto function composition (using `compose`) and partial application (currying).
While building the UI at wrightsnotes.com, I needed a better way of holding state and manipulating the DOM. The small amount of JS I had was becoming unmaintainable. In an attempt to a) understand all the code in my project and b) keep the payload small (< 12KB at time of writing) and chose to avoid frameworks and combine a few small modules do the job. In this talk I will detail how you can rock a framework-less flow while avoiding some of the issues that I ran into. Expect some reckons about the unix philosophy and other (polite) rants.