There are two types of complexity in coding: essential complexity stemming from the problem itself, and accidental complexity from things like frameworks and programming patterns. Accidental complexity can be eliminated by removing non-essential features from frameworks and generalizing and simplifying what remains. Functional programming techniques like pure functions that don't cause side effects can help reduce complexity by making code simpler to test and reuse.

1. Func.is
Simple > Complex

2. Why is coding so difficult?
2

3. Two types of Complexity
3

4. Types
 Essential complexity
 The problem itself
 System integration
 Differential usage
 Accidental complexity
 Frameworks, language features
 Architectural (anti)-patterns
 Object oriented programming?
4

5. How do we
eliminate
Func.is
accidental
complexity?
5

6. In terms of a framework
 Remove features untill there is nothing left (to
take away)
 Abstract and generalize what’s left
 Make it as simple as possible to use
6

7. Simple just ain’t easy!
Rich Hickey
http://www.infoq.com/presentations/Simple-Made-Easy
7

8. The causal event-flow
8

9. Let’s get practical
{Where} {What}
{Input}
{Output}
{When}
9

10. Pure functions
 The same input will always yield the same
output
 It doesn’t cause any side effects
 Simple to test, simple to reuse!
11

11. Side effects
 Conceptually difficult to handle with code
 Any computer program is irrelevant without
[side] effects.
 Side effects is an essential complexity
12

12. So where does it leaves
Func.is?
 Separation between what/when and how
 Good for building distributed systems
 The union between functional and flow-based
programming
 A better way to combine computer programs and
build big systems
13

13. Live Demo!
14