Skip to content
0:00 / 0:00

#elixir#erlang#community

ElixirConf 2015 - Keynote: Elixir Should Take Over the World by Jessica Kerr

Confreaks

42K subscribers • 83 videos on Hallway • Conference channel

YouTube
  • Recommended by 2 people: 1 on Lobsters and 1 curated list.
  • Presented by Jessica Kerr
  • An opinion. It argues one side of a question engineers disagree on.

Beginner. No background in the topic needed.

34K views11 years ago2 recommendations

Programming languagesTools and practiceElixir and ErlangCode review and teamworkDeveloper productivity

Jessica Kerr discusses how programming communities and businesses learn, improve their practices, and adopt models from other ecosystems.

Help us caption & translate this video! amara.org/v/HOmh/

Why it's here

2 people recommend this

What people say. Recommended as an earnest and upbeat talk about how programming communities learn and improve their practices.

programming-talkscurated list on GitHubRecommends

Under “Elixir”

Elixir Should Take Over the World 00:58:30 by **Jessica Kerr** (not only interesting for Elixir devs! But I wasn't sure where else to put it) (2015)

pushcxon Lobsters • Recommends

Keynote: Elixir Should Take Over the World Not cheerleading like the title implies. This is mostly about how communities and businesses learn, how we're improving our programming practice, models from other communities and the ismorphisms to familiar ones. Not just technically interesting, the talk is also unapologetically earnest and upbeat.

u/two_faced_commitin r/elixir • Mentions

Programming Phoenix: Step 1: Erlang, Step 2: Elixir, Step 3: Node.js - Wait, What!? So I went out and bought Programming Phoenix because Elixir really does look nice judging from the brochures and what better way to test its suitability for real-world stuff than writing a website. But then, on page 31 of 276 (page 22 if you go by the labels rather than the actual page number in the PDF), there's this marvel: > Web development often requires web assets to be processed for deployment. Rather than reinvent the wheel, developers can optionally use Node.js tools for those services. Phoenix will use brunch.io to compile static assets such as JavaScript and CSS by default, and Brunch.io uses npm…