Attending Edge Conference In NYC

Pssst... You're reading this on my old blog. You should update your RSS reader for my new one!

I've been invited to attend what looks to be an amazing event, Edge Conference.
Edge looked to be a different sort of conference, and I'm excited to see how it works.

Edge is about everyone learning from everyone else, so you need to bring something to teach as well as a desire to learn. Every moment of the conference will be publicly available afterward.

I hope that I can bring something to the discussion, and I feel that if I don't try to do so, I'm not getting as much as I could out of this. The format of Edge encourages and depends on it, in fact.

We open each hour long session with a ten minute talk. After that, we’re into the discussion, and we keep it moving fast. We record everything, on video and in text. Everything is released for free to the world the moment the event ends.

While I hope I'll be able to get in my two cents to what is sure to be a great crowd of brilliant people, I'm really excited about what I can learn from all of them. There are some people involved that I've looked up to for a long time, most notably Rob Hawks, Kumar McMillan, and how could I not mention Paul Irish?

I'm going to be aborbing a lot, and I'm going to bring it all back here. I hope to have some thoughts before the conference on the two topics I'm most interested in discussing: Offline and Responsive Images, and I can't wait to see how my understanding and opinions on all of the topics change with the conference.

Comments

Jeff Licquia said…

Pssst... You're reading this on my old blog. You should update your RSS reader for my new one!

Someone should tell Planet Python...

6:21 PM

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...

Developing Upwards

Search This Blog