There's a perception that Scala is too complicated.
In part that may come from cryptic compiler errors and hard to understand types.
You might be left wondering: what's the point?
Why am I trying to hack my way through cruft?

1. There's a way of writing simple Scala. A few straightforward ideas can be used again and again.You're using the power and flexibility of Scala, but in a sane way. This might not be the Scala you've heard about.

2. The type system enables us to do more. It's not just about checking for errors. These ideas from the world of functional programming aren't about being "clever" (in the bad sense). It's about a useful set of tools for everyday coding. This might not be the functional programming you've heard about.

The talk is in three parts:

• An example of what Scala looks like when using pattern matching over classes;
• How encoding an idea into types (using the "Combinable", or "monoid" if you prefer that kind of word); and
• Using advanced features of Scala (compile-time sized checked collections) without having to complicate our own code.

If you're Scala-curious, or heard that Scala or functional programming with types is just insanely complicated, this is the talk for you.