Everyone in the Fractal Slack channel is currently freaking out about this. Veeeeery iiiiinteresting!
Thanks to the quick work of Marc and his team, the talk I gave at Beyond Tellerrand on Thursday was online within hours!
I’m really pleased with how this turned out. I wasn’t sure if anybody was going to be interested in the deep dive into history that I took for the first 15 or 20 minutes, but lots of people told me that they really enjoyed that part, so that makes me happy.
This is the rarely-seen hour-long version of my Resilience talk. It’s the director’s cut, if you will, featuring an Arthur C. Clarke sub-plot that goes from the telegraph to the World Wide Web to the space elevator.
Here’s the closing keynote I gave at Frontend Conference in Zurich a couple of weeks back.
We work with technology every day. And every day it seems like there’s more and more technology to understand: graphic design tools, build tools, frameworks and libraries, not to mention new HTML, CSS and JavaScript features landing in browsers. How should we best choose which technologies to invest our time in? When we decide to weigh up the technology choices that confront us, what are the best criteria for doing that? This talk will help you evaluate tools and technologies in a way that best benefits the people who use the websites that we are designing and developing. Let’s take a look at some of the hottest new web technologies like service workers and web components. Together we will dig beneath the hype to find out whether they will really change life on the web for the better.
Matt Griffin’s thoughtful documentary is now available for free on Vimeo. It’s a lovely look at the past, present, and future of the web, marred only by the brief appearance of yours truly.
Here’s the video of the talk I gave at Smashing Conference in Barcelona last month—one of its last outings.
Measuring performance is important. Communicating the story of performance is equally important.
A design exercise for the Clearleft UI designers.
There’s probably a Pace Layer analogy in here somewhere.
Don’t replace. Augment.
I’m trying to understand why developers would trust third-party code more than a native browser feature.