Implementing Elm

A great time talking to Dan about more general development topics. Dan has a lot of practical advice and some opinions that I could not agree with more around failing fast, knowing how to identify what will bring value to your project and team communication.

Dan was a blast to talk to. He has a very real approach to development and hearing him talk about how "If I can do this anyone can" will give anyone the permission to shoot for that project you feel you cannot do.

Matthew and I dive deep into why he built elm-markup and the power that the Elm parser and types give you. You have to listen to this episode. Matthew is a really fun guy to talk to, but also a really smart one too and he breaks the implementation down in a way that will help anyone.

Another aftershow with Matthew where we discuss community, using domain knowledge and types can make complex projects easier, and sometimes forcing yourself to think how you use data by not using primitives in a project.

Another fun conversation after the implementation story stops. Jim has a lot of experience and wisdom to share so buckle up and enjoy the conversation.

In this episode Jim Carlson and I discuss how he brought Latex to the browser and made a better writing experience for Markdown and LaTex on the web.

In this after show episode Martin and I talk about how Elm empowers you as a developer to tackle the projects or problems that you did not feel confident in taking on in other languages.

In this episode I chat with Martin Janiczek to discuss how he built elm-browser and what it took him to build a custom elm text editor.

In this after show episode Brian and I talk about premortems, the most important skills he has learned the longer he works in Elm, and the main differences between large Elm applications and other small projects.

In this episode I chat with Brian Hicks from NoRedInk to discuss how they use a custom element to interface with Quill, a JavaScript rich text editor.

The reason for the this podcast is straightforward, to help Elm developers get better together by listening to real implementation stories from the people who have done the work. Elm as a language and the community are young and the amount of resources and examples from teams or individuals covering the details of implementing an Elm codebase could be better, and that is what I want to help with.