Phoenix

We’ve been dating for 7 years, and people ask us how we managed to stay together for so long. Our answers are: communication, transparency, and teamwork, all of which: we automated!

We want to show you how to build various tools using Node.js, APIs, and the Internet of Things, to make it easier to collaborate and set up routines. We'll bring our dynamic working together with conference speaking and improv experience to teach you about home automation while making you laugh a lot.

Testing your digital products with real people is the only real way to see if what you’ve built actually works. The problem is, many of us just don’t have the time or budget to run a full-scale usability test. Still, it’s always better to do some testing rather than none. We'll cover all the basics for running your own short, successful usability tests on a shoestring budget, using just a few basic resources.

The A/B test! We've all thought it: "What's the point? How much configuration do we need?" If you're familiar with the scientific method, those steps carve out the path to experimentation and A/B testing. Everyone loves a good hypothesis right? I know I do. Melding the world of science and software can help alleviate the stresses of experiments and help to maximize impact of every feature. In this talk we will journey through what an A/B test is, defining goals for A/B testing your app, and rolling out features based on successful experiments.

Atwood's law tells us that 'Any application that can be written in JavaScript, will eventually be written in JavaScript.'

We'll take that concept a bit further and creatively push the limits of the web platform and explore a few areas that could be better.

A fanciful journey following your code from conception in the editor through the awkward build processes into deployment pipelines out to the real world of public internet and off to it's final destination, being rendered in a user's browser.

The internet has become a complex place. With the advent of frameworks, build tools, and deployment services, the distance between developers and browsers is growing. Developer Experience has improved, but with these abstractions, we've introduced layers of obscurity.

This talk is intended for people with any level of experience, as it fills the gaps in knowledge of how things work. The information is not critical to your work, but it's fascinating nonetheless.

We'll take a deep dive into what happens after you hit save, what processes take place to get your code transformed for production, how does it get deployed, how it gets to the user, and the steps the browser takes to actually render the page.

When Neo asks Morpheus "What is the Matrix?", Morpheus' response is: "Control".

The JavaScript community has taken this to heart, what better way to take control than by creating your own framework or stack?

The only problem is, there's simply not enough of them. So we'll take a look at what it would take to create a stack-creation framework to help you make your own stack!

We'll quickly review the tools necessary for creating a stack (like code-generation scripts and coordinated task-running) to make everything expected/required for your stack and also discuss some of the practical and impractical applications, to make sure that we can control our Matrix before it controls us!