As developers, we don't deliver just code. We deliver change in the world.

• The value of software is in its connections to the wider system: in its use.
• Growth never stops until death; software is “done” when it’s out of production.
• We don’t grow -in- an environment; we grow -with- an environment. Influence is healthier than control.
• Teams are like forests. The whole forest is communicating underground through a network of roots and fungi. The essence of a team’s work is out of sight, in
• the knowledge we exchange with each other and embed into the software.
• Developers are like trees in a forest. Sometimes management can’t see the “team” for the “resources.”
• Trees are green because intensity isn’t everything. To go fast is less important than to keep going.

As developers, we don't deliver just code. We deliver change in the world.

• The value of software is in its connections to the wider system: in its use.
• Growth never stops until death; software is “done” when it’s out of production.
• We don’t grow -in- an environment; we grow -with- an environment. Influence is healthier than control.
• Teams are like forests. The whole forest is communicating underground through a network of roots and fungi. The essence of a team’s work is out of sight, in
• the knowledge we exchange with each other and embed into the software.
• Developers are like trees in a forest. Sometimes management can’t see the “team” for the “resources.”
• Trees are green because intensity isn’t everything. To go fast is less important than to keep going.

As developers, we don't deliver just code. We deliver change in the world.

• The value of software is in its connections to the wider system: in its use.
• Growth never stops until death; software is “done” when it’s out of production.
• We don’t grow -in- an environment; we grow -with- an environment. Influence is healthier than control.
• Teams are like forests. The whole forest is communicating underground through a network of roots and fungi. The essence of a team’s work is out of sight, in
• the knowledge we exchange with each other and embed into the software.
• Developers are like trees in a forest. Sometimes management can’t see the “team” for the “resources.”
• Trees are green because intensity isn’t everything. To go fast is less important than to keep going.

As developers, we don't deliver just code. We deliver change in the world.

• The value of software is in its connections to the wider system: in its use.
• Growth never stops until death; software is “done” when it’s out of production.
• We don’t grow -in- an environment; we grow -with- an environment. Influence is healthier than control.
• Teams are like forests. The whole forest is communicating underground through a network of roots and fungi. The essence of a team’s work is out of sight, in
• the knowledge we exchange with each other and embed into the software.
• Developers are like trees in a forest. Sometimes management can’t see the “team” for the “resources.”
• Trees are green because intensity isn’t everything. To go fast is less important than to keep going.

What do you get when you combine strict functional programming with heavy user interaction?

Challenges, and unexpected freedoms.

Elm is a purely functional language for the browser. It compiles to JavaScript – after enforcing immutability, types, semantic versioning, and tight boundaries for user and server interactions. Working within these restrictions, I find my programming principles turned upside down. Small components? who needs them. Global state? no problem. New principles emerge instead: events, reproducibility, kindness in times of error. This session gives an overview of Elm, then focuses on the Elm Architecture. See how this lets me do front end development like never before: free of runtime errors, full of joy and possibilities.

KEYWORDS

JavaScript, Elm, Web, Functional, Event Sourcing, Architecture, Languages

What do you get when you combine strict functional programming with heavy user interaction?

Challenges, and unexpected freedoms.

Elm is a purely functional language for the browser. It compiles to JavaScript – after enforcing immutability, types, semantic versioning, and tight boundaries for user and server interactions. Working within these restrictions, I find my programming principles turned upside down. Small components? who needs them. Global state? no problem. New principles emerge instead: events, reproducibility, kindness in times of error. This session gives an overview of Elm, then focuses on the Elm Architecture. See how this lets me do front end development like never before: free of runtime errors, full of joy and possibilities.

KEYWORDS

JavaScript, Elm, Web, Functional, Event Sourcing, Architecture, Languages

What do you get when you combine strict functional programming with heavy user interaction?

Challenges, and unexpected freedoms.

Elm is a purely functional language for the browser. It compiles to JavaScript – after enforcing immutability, types, semantic versioning, and tight boundaries for user and server interactions. Working within these restrictions, I find my programming principles turned upside down. Small components? who needs them. Global state? no problem. New principles emerge instead: events, reproducibility, kindness in times of error. This session gives an overview of Elm, then focuses on the Elm Architecture. See how this lets me do front end development like never before: free of runtime errors, full of joy and possibilities.

KEYWORDS

JavaScript, Elm, Web, Functional, Event Sourcing, Architecture, Languages

Programming is a series of frustrations. Everything we do, we could do better or faster if we only had our tools set up just so. If our error messages were a little better, our code a little cleaner, our tests a lot wider. When we spend time on this, it's known as "yak shaving," and it can get messy.

How do you balance the work you’re supposed to be doing with the work that makes your work, work? Dive into the yak stack with me. We'll see five different species of yak, and discuss how and when to tackle each one. At the bottom of the yak stack, we might find the Golden Yak, with secret wisdom engraved on its skin.

This session will give you reasons to spend time smoothing your development experience, and clues for where to spend that time in ways that help your whole team.

Programming is a series of frustrations. Everything we do, we could do better or faster if we only had our tools set up just so. If our error messages were a little better, our code a little cleaner, our tests a lot wider. When we spend time on this, it's known as "yak shaving," and it can get messy.

How do you balance the work you’re supposed to be doing with the work that makes your work, work? Dive into the yak stack with me. We'll see five different species of yak, and discuss how and when to tackle each one. At the bottom of the yak stack, we might find the Golden Yak, with secret wisdom engraved on its skin.

This session will give you reasons to spend time smoothing your development experience, and clues for where to spend that time in ways that help your whole team.

Programming is a series of frustrations. Everything we do, we could do better or faster if we only had our tools set up just so. If our error messages were a little better, our code a little cleaner, our tests a lot wider. When we spend time on this, it's known as "yak shaving," and it can get messy.

How do you balance the work you’re supposed to be doing with the work that makes your work, work? Dive into the yak stack with me. We'll see five different species of yak, and discuss how and when to tackle each one. At the bottom of the yak stack, we might find the Golden Yak, with secret wisdom engraved on its skin.

This session will give you reasons to spend time smoothing your development experience, and clues for where to spend that time in ways that help your whole team.

There’s a story to tell, about musicians, artists, philosophers, scientists, and then programmers.

There’s a truth inside it that leads to a new view of work, that sees beauty in the painful complexity that is software development.

Starting from The Journal of the History of Ideas, Jessica traces the concept of an “invisible college” through music and art and science to programming. She finds the dark truth behind the 10x developer, a real definition of “Senior Developer” and a new name for our work and our teams.

There’s a story to tell, about musicians, artists, philosophers, scientists, and then programmers.

There’s a truth inside it that leads to a new view of work, that sees beauty in the painful complexity that is software development.

Starting from The Journal of the History of Ideas, Jessica traces the concept of an “invisible college” through music and art and science to programming. She finds the dark truth behind the 10x developer, a real definition of “Senior Developer” and a new name for our work and our teams.

There’s a story to tell, about musicians, artists, philosophers, scientists, and then programmers.

There’s a truth inside it that leads to a new view of work, that sees beauty in the painful complexity that is software development.

Starting from The Journal of the History of Ideas, Jessica traces the concept of an “invisible college” through music and art and science to programming. She finds the dark truth behind the 10x developer, a real definition of “Senior Developer” and a new name for our work and our teams.