Hi!

Pipe forward |> Using Elixir and F# together

Elixir and F# are two languages that are loved by their users (and for good reasons). Both are functional. Both are expressive. Both are growing up as the smarter, cooler, prettier younger sibling in their families. Both share the elegant pipe operator "|>". And that (screech) has pretty much exhausted the list of their similarities.

In most other ways they are different, and they are good at different things. F# has a great type system. Elixir has a great concurrency model. F# can run on mobile devices. Elixir can handle requests from millions of mobile devices. Even the timescales of their sweet spots differ.

If both deserve a place in our toolbox how can we use them together? We will explore various interoperability techniques (from loose to tight), and we'll develop an intuition for which hammer not to use on which thumb.

What every Node.js developer needs to know about Elixir

Node with its sweet-spot of quickly standing up back-ends has caught fire in dev shops around the world. Depending on your business case, that fire can yield a high-fiving “we did it!” celebration, or a charred project timeline with scorched, haggard developers. When is Node OK? When is it dangerous? What’s the alternative?

Many seasoned Node developers are discovering Elixir makes a great lifeline when Node turns creepy. They're escaping to a polyglot approach: JavaScript in the browser, Elixir on the server. OK… but why Elixir? Answer: Elixir is approachable and productive like Node, but it’s much more versatile and safe than Node.

Elixir is an expressive functional programming language that is 100% "good parts” borrowed from Erlang, Ruby, Clojure, Python, F#, and Node.js. Elixir delivers familiar (modern) tooling, developer joy, simplified distribution, massive concurrency, and carrier grade fault-tolerance. Curious? Good! Come join the fun!

Show 1163 - Lean Functional with Bryan Hunter

"Isn't all functional programming lean? What does that even mean? While at NDC, Carl and Richard chatted with Bryan Hunter about lean principles and how they apply to functional programming. After a quick debate around the merits of object-oriented programming vs functional programming, the conversation turns to the history and principles of lean. Bryan shows how lean informs your approaches to programming, how you can evaluate your tooling and techniques to build the best software possible. Is functional programming the ultimate manifestation of lean?"

Lean and Functional Programming

Companies adopt Lean because it is a proven path to improving delivery times, reducing cost, and improving quality. A company that writes software cannot truly embrace Lean without also embracing functional programming. Why? Lean is about building quality into the process. Lean is a systemic method for reducing waste, overburden, and inconsistency. With OO, many forms of waste, overburden, and inconsistency are unavoidable. A defect early in the process always results in a defect in the product later in the process, and OO itself is a defective process. In this session we will go from the origins of both Lean and FP and see how specific FP concepts (examples in F#, Elixir) map onto Lean principles. We will also discuss why some companies fail at Lean and FP.

Show 1080 - Programming Elixir with Bryan Hunter

"Isn't all functional programming lean? What does that even mean? While at NDC, Carl and Richard chatted with Bryan Hunter about lean principles and how they apply to functional programming. After a quick debate around the merits of object-oriented programming vs functional programming, the conversation turns to the history and principles of lean. Bryan shows how lean informs your approaches to programming, how you can evaluate your tooling and techniques to build the best software possible. Is functional programming the ultimate manifestation of lean?"