Skip to main content

EdgeConf 2013 Was The Best Conference I've Ever Attended

I do not say this lightly. I have a strong emotional bond with PyCon, and I’ve run my own conference. EdgeConf was easily the most rewarding conference experience I’ve ever had the pleasure to be a part of. Capturing why it was such a great time is very important to me.

EdgeConf was a combation of validation, fascination, and exploration.

I attended EdgeConf feeling a bit apprehensive. To me, it seemed like a Big Deal full of amazing people I would feel completely out of place around. I did not expect to fit in, but to just absorb from these smart people.

What I found instead were experts on panels solving the same problems I’m solving in very similar ways, making different trade-offs. I learned how Conde Nast has been loading responsive images, something I’ve implemented and maintain, and spent considerable time at dinner comparing the approaches we’ve taken. I was able to learn about Javascript-free ways to implement our loader, with browser support trade-offs using “The Clown Car” technique. And, I think, I was able to impart a bit of our own successes in moving our image sizing out of the content and into the presentation layer.

I was absolutely fascinated by the Legacy and Payment panels, the two I thought I’d be bored by. When Manu Sporny from the W3C told us to come and get involved in defining the spec, and when questions were routinely responded to with “go write a spec for it”, I felt enormously empowered as a participant in the direction of the web.

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...

Using a React Context as a Dispatch Replacement

React Contexts are the pretty little bows of the React world. Here's a really quick example of the kind of messy code you can cleanup by using contexts, without dragging in a larger dependency like Redux or even Flux. Starting backwards with a diff showing lines of code I was able to remove: All the properties I was able to remove were just pass-through. The Carousel component didn't care about any of them, but it had to pass through these callbacks so the multiple TaskList components inside the carousel could invoke actions. They were removed from the Component class itself, too, since it no longer needed to pass them through. Where did they all go? My ActionContext removed all the need for these passthroughs by providing a single simple helper method, action(), that components rendered under it can access.   I really enjoy the pattern of passing a single callback through a context and removing what used to be lots of callback properties. Of course, I cou...