Elm Radio

• Georges Boris (twitter) (github)
• elm-book
• Elixir's Hex docs
• Leaf lang docs site (built with elm-book)
• elm-verify-examples
• elm-book in elm-book guide
• elm-visualization examples site
• elm-charts site
• elm-widgets (alpha package docs)
• elm-admin (alpha package docs)
• elm-ui-explorer (alternative Elm storybook style framework - comes with knobs)
• dmy's Elm package repo site
• dmy's github
• elm-graphql selection set docs page (reads like a tutorial top to bottom)
• uncover.co

• Alex Russell's post Platform Adjacency Theory
• VoiceOver rotor utility
• Use semantic HTML to improve screen reader experiences
• Forms - use onsubmit with a form to get nice keyboard handling and screen reader accessibility
• datetime-local tags
• MDN docs for sending form data
• HTMHell (examples of non-standard HTML from the wild and why it matters)
• Dillon's Use the Platform blog post

• Incremental Steps episode

• Built-in quality (from Lean principles)

• Tiny commits

• Kent Beck's book TDD by example

• Dead Code episode

• Close open loops

• Getting Things Done (GTD) methodology

• Capturing

• Processing

• Pomodoro Method

• rainymood.com

• Centered App

• Trunk-based development

• elm-review template flag (preview folder)

• sparksp/elm-review-no-forbidden-words

• Self-documenting code

• Self-documenting code tweet and blog post

• elm-verify-examples

• API Design Lessons episode

• Hammock-Driven Development

• Releasing vs. shipping

• Continuous Delivery

• Naming as a Process article by Arlo Belshee

• Oxbow code (code that was once used but is no longer in use)
• Jeroen's elm-review-unused elm-review rule
• Jeroen's blog post Safe dead code removal in a pure functional language blog post
• elm-review-simplify
• Getting Things Done (GTD) methodology
• Inbox Zero
• Jeroen's no-extraneous-dependencies rule
• Try out elm-review-unused with elm-review --template jfmengels/elm-review-unused/example
• Jeroen's You thought you had no dead code post

• Joël Quenneville (Twitter)
• Elm's Universal Pattern episode
• List.concatMap is the same pattern as andThen under a different name
• andThen identity can be used to flatten something
• Dillon's Combinators article
• Martin Janiczek's elm-list-cartesian package gives two valid map2 implementions for List
• Monoid - need a way of having something empty, and way to combine two things - for example addition for numbers starting with 0
• Jeroen's elm-review-simplify package

More of Joël's distillation of category theory ideas:

• Running out of maps (applicatives)
• The Mechanics of Maybe (taking maybe apart and putting it back together)
• Two ways of looking at map functions (functors)
• Elm's universal pattern (applicatives)
• Inverting a binary tree (folding, catamorphisms)
• Joël's directory of blog posts on the ThoughtBot blog

• Solving the Boolean Identity Crisis (Elm Conf talk by Jeremy Fairbank)
• If It Compiles, It Works episode
• Opaque Types episode
• Life of a File talk by Evan Czaplicki
• Roc language
• ianmackenzie/elm-units package
• Parse, Don't Validate episode
• Using Semantic Types to Squash Bugs - Dillon's talk where he walks through the mechnical steps to safely introduce a wrapper type
• Dillon's Entry Gatekeepers blog post

• Ju Liu (twitter) (github)
• Elm at NoRedInk
• Ju's blog
• noredink-ui is NoRedInk's internal UI kit (live demo page)
• avh4/elm-program-test
• elm-sortable-table API
• Implementing Elm Podcast season 1
• cultureamp/react-elm-components (React library for embedding Elm as a Web Component)
• elm-community/js-integration-examples
• NoRedInk is hiring Elm and Haskell devs
• Ju Liu's blog

• Robin Hansen (twitter) (github)
• elm-optimize-level-2
• Html.Lazy API
• Outperforming Imperative with Pure Functional Languages - talk about Roc by Richard Feldman
• Tail call optimization
• Successes, and failures, in optimizing Elm’s runtime performance - Robin's blog post series on his elm-optimize-level-2 optimizations
• WASM
• Maybe you don't need Rust and WASM to speed up your JS
• Brian Carroll's blog posts on an Elm WASM prototype
• Robin's Stabel language - a stack oriented language that compiles to WASM
• What's Working for Elm Elm Radio episode
• Process.elm comment about the potential for parallelizing work

• Dillon's blog posts If It Compiles It Works and When It Compiles But Doesn't Work
• Wiring
• Refactoring
• Running code paths to check it works vs checking assumptions at the gate
• Dillon's talk Types Without Borders
• Shotgun surgery - Parse, Don't Validate episode
• Order independent
• You can trust your tests
• Keeping what you depend on to a minimum helps make things trustworthy
• Semantics can make it harder to predict (like parser)
• Json.Decode.maybe is almost never what you intend
• Scaling Elm Apps talk by Richard Feldman
• Gary Bernhardt's Wat video
• Elm Radio Opaque types episode

• Woody Zuill on Turn Up the Good
• Mob Programming

• Elm 0.19 removing side effects
• Purity is what makes elm-review interesting
• Jeroen's post Safe dead code removal in a pure functional language
• No runtime exceptions

Useful error messages

• Evan's 2017 Deconstructconf talk Evan Czaplicki On Storytelling
• Evan's talk What is Success?

• Isomorphic code
• Meta frameworks (elm-pages, Lamdera, elm-spa)

• The community can iterate quickly and experiment with new changes
• elm-optimize-level-2 and elm-format are great examples
• elm-optimize-level-2 can make their way upstream and don't break Elm's guarantees or assumptions
• Robin Hansen's blog post series Successes, and failures, in optimizing Elm’s runtime performance
• Extensible Web Manifesto
• Platform should provide building blocks, not solve every specific use case

• Stable data layer, architecture allows ecosystem to evolve around it with less churn

• People passionate about a problem working on it in the ecosystem

• Leveraging Elm's unique characteristics for performance (immutability, static language, known types, etc.)
• Elm compiler performance - compiler speed matters

• Elm community content and conferences
• Elm Online meetdown

• Evan's Elm philosophy tweet
• Philosophy has influenced package design in the ecosystem
• Elm Slack #api-design channel