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

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

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 operate on. The only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…