Podcast appearances and mentions of paul chiusano

In this week’s episode of Elixir Mix the panel interviews Chris Keathley about Norm and his recent talk at ElixirConf. Chris is currently working at Bleacher Report, working mostly on backend systems. The panel starts by complimenting his presentation skills and asking him about his dislike for dialyzer.    Chris share the many problems he has with dialyzer. Dialyzer takes a lot of time and has crappy ergonomics. While it tells you a lot about an Erlang system that benefit doesn’t extend to Elixir systems. Neither doesn’t understand protocols. Mostly he feels that most type algebras don’t allow for growth, making changes and making the breaking changes. Explaining that type systems all have their costs and benefits, he feels that you don’t see the benefits of dialyzer until your system is up and running.   The panel wonders about Norm, a library written by Chris. Chris explains what it is and what its aims are. He wrote the library to solve some of the problems seen with dialyzer and other problems he was having at work. It is mostly for validating data. He wanted to be able to put checks in where ever he wanted and to make it very hard to break systems. Norm lets you describe data in your system, by taking an arbitrary predicate and making it into a spec. Chris explains how this works and how it will not make any changes until you tell it to. He shares some of the other features offered by Norm.    The sweet spot for using Norm is the next subject broached by the panel. Chirs explains that Norm fits well into the boundaries of systems, this is the most obvious place and the best place to start. The least intuitive way Chris has used Norm is to specify the options you need to pass to gen servers. He explains that it is not the most obvious use for Norm but it has been really helpful with the API.   Next, the panel asks about changesets and how that works with Norm. Chris explains that changesets are very specific while Norm allows more freedom. The biggest difference between the two is that Norm won’t do casting for you. They intentionally built Norm that way because of the way Bleacher Report uses string and atom keys.    In his talk, Chris explains the concept of design by contract. It means that for every function that you have you can specify preconditions and postconditions. Preconditions are things that have to be true prior to calling the function. Postconditions are things that have to be true after the functions been called. Right now Norm doesn’t provide preconditions and postconditions which provides a way to avoid some of the more expensive costs in production.   Chris uses Norm in all his opensource projects and in projects at work. He shares the benefits he has seen. He believes that most systems will see benefits from Norm if they have room to grow. In his experience, every time they run into something new and think they may need to expand or change Norm, they find that Norm already has everything they need. Chris asks listeners who want to help contribute to Norm to try it out and to give him feedback. Panelists Mark Ericksen Eric Oestrich Josh Adams Guest Chris Keathley Sponsors   Sentry– use the code “devchat” for two months free on Sentry’s small plan Adventures in Blockchain React Round Up CacheFly Links ElixirConf 2019 - Contracts for Building Reliable Systems - Chris Keathley https://github.com/keathley/norm EMx 040: Elixir Outlaws and Adopting Elixir with Chris Keathley EMx 003: Chris Keathley https://keathley.io  https://twitter.com/chriskeathley?lang=en https://elixiroutlaws.com/  https://en.wikipedia.org/wiki/Design_by_contract  https://www.facebook.com/Elixir-Mix  https://twitter.com/elixir_mix Picks Mark Ericksen: zFRAG  Eric Oestrich: War Machine  Josh Adams: "Unison: a new distributed programming language" by Paul Chiusano https://github.com/unisonweb/unison  Chris Keathley: Daniels' Running Formula 

In this week’s episode of Elixir Mix the panel interviews Chris Keathley about Norm and his recent talk at ElixirConf. Chris is currently working at Bleacher Report, working mostly on backend systems. The panel starts by complimenting his presentation skills and asking him about his dislike for dialyzer.    Chris share the many problems he has with dialyzer. Dialyzer takes a lot of time and has crappy ergonomics. While it tells you a lot about an Erlang system that benefit doesn’t extend to Elixir systems. Neither doesn’t understand protocols. Mostly he feels that most type algebras don’t allow for growth, making changes and making the breaking changes. Explaining that type systems all have their costs and benefits, he feels that you don’t see the benefits of dialyzer until your system is up and running.   The panel wonders about Norm, a library written by Chris. Chris explains what it is and what its aims are. He wrote the library to solve some of the problems seen with dialyzer and other problems he was having at work. It is mostly for validating data. He wanted to be able to put checks in where ever he wanted and to make it very hard to break systems. Norm lets you describe data in your system, by taking an arbitrary predicate and making it into a spec. Chris explains how this works and how it will not make any changes until you tell it to. He shares some of the other features offered by Norm.    The sweet spot for using Norm is the next subject broached by the panel. Chirs explains that Norm fits well into the boundaries of systems, this is the most obvious place and the best place to start. The least intuitive way Chris has used Norm is to specify the options you need to pass to gen servers. He explains that it is not the most obvious use for Norm but it has been really helpful with the API.   Next, the panel asks about changesets and how that works with Norm. Chris explains that changesets are very specific while Norm allows more freedom. The biggest difference between the two is that Norm won’t do casting for you. They intentionally built Norm that way because of the way Bleacher Report uses string and atom keys.    In his talk, Chris explains the concept of design by contract. It means that for every function that you have you can specify preconditions and postconditions. Preconditions are things that have to be true prior to calling the function. Postconditions are things that have to be true after the functions been called. Right now Norm doesn’t provide preconditions and postconditions which provides a way to avoid some of the more expensive costs in production.   Chris uses Norm in all his opensource projects and in projects at work. He shares the benefits he has seen. He believes that most systems will see benefits from Norm if they have room to grow. In his experience, every time they run into something new and think they may need to expand or change Norm, they find that Norm already has everything they need. Chris asks listeners who want to help contribute to Norm to try it out and to give him feedback. Panelists Mark Ericksen Eric Oestrich Josh Adams Guest Chris Keathley Sponsors   Sentry– use the code “devchat” for two months free on Sentry’s small plan Adventures in Blockchain React Round Up CacheFly Links ElixirConf 2019 - Contracts for Building Reliable Systems - Chris Keathley https://github.com/keathley/norm EMx 040: Elixir Outlaws and Adopting Elixir with Chris Keathley EMx 003: Chris Keathley https://keathley.io  https://twitter.com/chriskeathley?lang=en https://elixiroutlaws.com/  https://en.wikipedia.org/wiki/Design_by_contract  https://www.facebook.com/Elixir-Mix  https://twitter.com/elixir_mix Picks Mark Ericksen: zFRAG  Eric Oestrich: War Machine  Josh Adams: "Unison: a new distributed programming language" by Paul Chiusano https://github.com/unisonweb/unison  Chris Keathley: Daniels' Running Formula 

It's time to talk about Functional Programming. Chris Bimson hosting, with Gabriele Cipriano, Richard Wild, and Jorge Gueorguiev Garcia given their opinions We mention briefly the books: Purescript by Example by Phil Freeman and Functional Programming in Scala by Paul Chiusano and Runar Bjarnason. Photo: Prairie Dog by DigiPD is licensed under CC0Music: "Sweeter Vermouth" by Kevin MacLeod is licensed under CC-BY 3.0

Panel: Nader Dabit Special Guests: Paul Gray In this episode of React Round Up, the panel discusses the future of higher order components and render props with Paul Gray. Paul is a software developer at an educational technology company called Learning Objects. They have a learning platform there that helps instructional designers create better contents. They talk about how he got into programming and React, when you would want to use HOCs and render props, and chainable components. In particular, we dive pretty deep on: Paul intro React How long have you been working with React? How did you get into programming? TI-89 Calculators in high school Software engineering degree in college Big fan of HOCs when they came out Chainable components Chainable components API Promises Anatomy of render prop components TypeScript async/await GitHub Gist Use cases Tool to share reusable code in React How long has this been in the works? With State Mapp Chain function Functional Programming Functional Programming in Scala by Paul Chiusano And much, much more! Links: Learning Objects React Chainable components TypeScript async/await GitHub Gist Functional Programming in Scala by Paul Chiusano Paul’s GitHub PaulGray.net Picks: Nader Viro React Expo blog Paul The Great Interior Design Challenge Little Tikes Red Car

Panel: Nader Dabit Special Guests: Paul Gray In this episode of React Round Up, the panel discusses the future of higher order components and render props with Paul Gray. Paul is a software developer at an educational technology company called Learning Objects. They have a learning platform there that helps instructional designers create better contents. They talk about how he got into programming and React, when you would want to use HOCs and render props, and chainable components. In particular, we dive pretty deep on: Paul intro React How long have you been working with React? How did you get into programming? TI-89 Calculators in high school Software engineering degree in college Big fan of HOCs when they came out Chainable components Chainable components API Promises Anatomy of render prop components TypeScript async/await GitHub Gist Use cases Tool to share reusable code in React How long has this been in the works? With State Mapp Chain function Functional Programming Functional Programming in Scala by Paul Chiusano And much, much more! Links: Learning Objects React Chainable components TypeScript async/await GitHub Gist Functional Programming in Scala by Paul Chiusano Paul’s GitHub PaulGray.net Picks: Nader Viro React Expo blog Paul The Great Interior Design Challenge Little Tikes Red Car

In this episode I speak with Paul Chiusano (@pchiusano), creator of Unison, about his ambitious vision for the future, where we can abstract over distributed computing, and there are no apps.