SESSION + Live Q&A
Full-Scale Elm in Production
Elm is a functional programming language that compiles to performant JavaScript. At NoRedInk we have over 80,000 lines of production Elm code. It's the primary technology we use to build our Web application's user interface, which students around the world use to answer millions of questions per day. Since we began using Elm in 2015, our production Elm code has yet to cause a single runtime exception. Our error logs show plenty of crashes from our legacy JavaScript code, but none from our Elm code. We've also found our Elm-powered front-end substantially easier to scale than our previous React code base. In this talk, attendees will gain an understanding of how the Elm programming language works, what differentiates it from the other front-end technologies on the market, and practical advice for introducing it to an existing JavaScript code base. The talk will contextualize all this in an experience report of shipping production Elm code, including how it has impacted our team's velocity, technical debt, and hiring. Attendees are assumed to be comfortable with JavaScript, but no other knowledge is needed. Come see how nice your team's front-end programming experience can become!
Speaker
![](https://archive.qconlondon.com/sites/qcon_london/files/styles/240x240/public/profille-green-shirt.jpg?itok=-quR-7yj)
Richard Feldman
Elm Pioneer & Software Engineer @noredink
Richard is the author of “Elm in Action” from Manning Publications, and the instructor for the Frontend Masters 2-Day Elm Workshop. When he’s not writing about Elm, teaching Elm, speaking about Elm, or co-hosting the San Francisco Elm meetup, he likes to take a break from his job at...
Read moreFind Richard Feldman at:
From the same track
Adventures in JavaScript and the IoT
From installations to promote superstar DJs on trains speeding across Europe to sitting in Motorway LED billboards debugging wi-fi cards when the temperature drops below zero, our experience building for the IoT has highlighted just how unpredictable failure can be. This talk is a warts and all...
![](https://archive.qconlondon.com/sites/qcon_london/files/styles/240x240/public/image001.jpg?itok=s1uPkkna)
James Hall
Founder/Director @Parallax
The Hitchhiker's Guide to Serverless Javascript
Tools like AWS’s Lambda, Google's Cloud Functions, and many others are allowing us to create “serverless” applications. At Bustle (a top 30 website in the US) we are taking full advantage of this new infrastructure. APIs, databases, searching, indexing, server side rendered javascript, are...
![](https://archive.qconlondon.com/sites/qcon_london/files/styles/240x240/public/steve_3_of_9_1.jpg?itok=VI2gZHhh)
Steve Faulkner
Director of Engineering @Bustle
Rebuilding The Monolith With Composable Apps
Working with JavaScript is exciting. There's constant change - in the language, the runtimes and the community. The last 24 months have seen the rise and fall of frameworks, libraries, platforms and best practises. All this change is great if you have the option to build smaller products, either...
![](https://archive.qconlondon.com/sites/qcon_london/files/styles/240x240/public/pictures/ian_thomas.jpg?itok=SlnaWHps)
Ian Thomas
Senior Principal Engineer @thestarsgroup
Microservices At The Heart of BBC iPlayer
The BBC iPlayer API used to be a monolithic Java application. Two years ago we switched to Node.js microservices and we have been iterating on it ever since. We have learnt many things along the way including how to keep distributed systems decoupled, how to monitor the health of our services in...
![](https://archive.qconlondon.com/sites/qcon_london/files/styles/240x240/public/cem_staveley_headshot_0.png?itok=64uBJv2C)
Cem Staveley
Software Engineer @BBC iPlayer