With O'Reilly's Fluent Conference right around the corner, I felt it was a good time to catchup with Peter Cooper who helps chair the event. In case you didn't know, Fluent is one of the premier developer events in the world, bringing together top speakers like Brendan Eich, Paul Irish, Lea Verou, Burke Holland and many others to delve out amazing presentations on modern web development.
Peter himself is a household name built on his contributions in the Rails world and his awesome set of email newsletters (really worth checking out!).
I got an opportunity to ask him a few questions about managing such a huge conference and the state of the Web Platform. Let's check it out.
Let's start off with an intro. Mind telling us a bit about yourself, Peter?
One of your big yearly initiatives is helping drive O'Reilly's Fluent Conference. Why is this such an important thing for you and the developer community?
On the surface, I'm an unusual person to chair an event like Fluent. I tend not to go to many conferences as they aren't a natural fit for the hermit-like way I like to learn and network. I'm about as introverted as it gets. When the opportunity came up, however, I simply had to get involved for the learning experience and to help flex my social muscles a bit.
Ultimately I've got to learn a lot about conference organization, what makes attendees tick, and what makes an event work (or not). One thing I've learned is that for most conference attendees, events like Fluent help make the amorphous online “communities” around languages and technologies “real.” People get to meet folks they admire, whose Twitter accounts they follow, and whose tools and code they use. Most attendees also devote themselves to getting involved with on-site events, interacting with speakers, and learning in a way that so few people can do purely with blog posts or online video.
Real life events only seem to be becoming more popular in the developer community, and in an increasing number of forms, both formal and informal. Anyone who can provide the right people, the right venues, and the right activities to the right attendee base is going to be successful.
Conferences are always positioned as an opportunity to learn something new. From an educational standpoint, what are the challenges you face with a conference of this size for ensuring you're getting relevant and up-to-date presentations in place?
Our biggest challenge is timing. Being a company of a certain size, O'Reilly has a variety of processes in place to make sure that the organization of their conferences runs smoothly. Part of this means we have to run our CFP (Call For Speakers) several months in advance and this can be problematic in a fast moving area like Web development as some speakers aren't allowed to disclose things they're working on yet or they might not know when certain features will be publicly usable or not (Web Components and Polymer are key examples this year).
Big conferences can be overwhelming to attendees. What have you found to be the best way for someone to learn something new while they're at an event?
It's hard to say, as people seem to learn in such different ways. To a certain extent, I think attendees self select themselves to the variety of ways we offer up content. Rather than offer fixed, three hour workshops and 50 minute talks this year, we've opened up the format a bit with a variety of shorter and longer workshops, shorter talks, and various on-site events and meet-ups, giving people a better chance of finding the approaches that work for them.
Ultimately, though, I don't think the key point of conferences is to formally learn things, although that's a good point to lean on, particularly when convincing bosses to let you attend! Being inspired, getting a feel for what's going on in the field, and networking are all more important and likely to have a bigger effect on attendees' careers, and we aim to provide all three.
Along the lines of education, developer tooling and workflow has evolved quite a bit and continues to change frequently with new tools sprouting up daily. What can developers do to stay on top of this evolution and not get left behind?
As someone who publishes a variety of developer newsletters, I should be quick to recommend weekly newsletters as a great way to stay up to date, but really there are a ton of ways from following interesting people on Twitter and subscribing to interesting publications (like yours!) through to podcasts and YouTube channels.
Perhaps the best mechanism for keeping up to date in a broad sense nowadays is Twitter. Whereas publications and newsletters might have their own agendas or biases, following a wide variety of people in your industry on Twitter is a guaranteed way to get a feel for what public opinion is, what tools people are using, and what's going on. It takes time and a lot of patience to use Twitter properly, but it can be very rewarding, especially when you participate yourself.
With modern browsers becoming more powerful, what are the new technologies you see that will have a dramatic impact on how we build web applications in the future (for example, Polymer, Web RTC)?
A variety of multimedia and graphical APIs seem to be having a bigger impact in the mid-term, including WebGL (now finally supported by all major desktop browsers except Safari), HTML5 Canvas, the video and audio tags, and WebRTC's getUserMedia. These are having a huge impact in terms of taking over in a variety of popular areas that Flash has been the dominant technology, for the past decade.
What remains to be seen (and enjoyed!) is how developers will tie all of these technologies together because in terms of commercial examples, we've mostly been seeing reproductions of Flash-level approaches so far, but the widespread proliferation and availability of all of the exciting Web Platform APIs under development is going to open up a wide variety of new opportunities.
Both of the frameworks I've mentioned above have opinionated workflows. Shouldn't some of their patterns and components just be a part of the Web Platform itself so we can have some level of standardization?
You could argue that many libraries and frameworks are essentially large-scale ‘polyfills' for gaps in the Web Platform, but I personally believe it's necessary for them to fight for survival and thrive as external, third party systems because that's the only way good ideas get proven and bad ideas die. I certainly don't think bodies like the W3C and WHATWG should be the principal drivers of innovation on the Web, instead of responding to and augmenting the innovation already taking place.
In terms of the Web Platform, it seems we can ask a similar question about standards support. We're still being held back in some respects by browser fragmentation, especially in mobile. How long do you see this persisting, requiring continued use of polyfills and shims? Should we just forget about older browsers?
One of the biggest effects on rolling out new technologies has come along with browsers that automatically update, a feature now mainstream in Chrome, Firefox, and Internet Explorer. People are stuck on older browsers for a rapidly decreasing amount of time, although there'll still be an un-shiftable percentage of hold-outs, particularly those forced to be on older versions under enterprise policies or due to aging hardware.
Progressive enhancement has been repeatedly pitched as a partial solution to the problem. If someone's working on an older browser, the features that their browser can support will still be available, for example. In reality, though, progressive enhancement is hard and many developers and companies are finding it easier to draw lines in the sand of what browsers they'll support (like Google's recent announcement that they're dropping support for IE9 in their apps).
Part of this browser fragmentation is driven by the enterprise community's slower update cycles. Being respectful of their needs for stability, how do we help nudge them along so they can not only leverage the new and exciting capabilities of the Web Platform but also not hold back the platform?
Being what they are, enterprises are likely to remain relatively conservative, but auto update features are still making it into companies where strict adherence to versioning policies isn't mandated. A big lever, is that enterprises are now more likely to rely on third party apps like Google Apps or 37signals' Basecamp rather than internal intranets, so the control over which browsers get used increasingly comes down to a tug-of-war negotiation between SaaS providers and their customers, rather than solely down to the customers.
I honestly don't know how he does it. Between running a monster event, managing an incredibly popular weekly set of mailing lists (they need to be curated) and of course, actually doing work, it's incredible how he has time to even have a meal. So Peter, I'm grateful for you spending some time answering our questions, especially with Fluent approaching quickly.
I'll be at the conference myself and hopefully you can join Tuts+ at Fluent 2014. Save 20% by registering here with code TUTS+20. See you there!
Envato Tuts+ tutorials are translated into other languages by our community members—you can be involved too!Translate this post