1. Its in F*ckin' New York City!
I know NYC isn't for everyone but there's everything you could imagine here. On top of learning and getting inspired about Flash you'll have everything NYC has to offer at your finger tips. The organizers of the conference know this and have created what they call the "City Track". They've organized a few "field trips" throughout the city that you can tag along with. Just think of all the cool stuff you'll be able to check out, eat, and do while you're here!

2. Its at the 3-Legged Dog Art & Technology Center
This place is just plain cool. Its entirely artist-run and have been supporting the arts in NYC since the center was built in 2006 just three blocks south of the WTC site. Personally, it feels good to be supporting such an organization.

3. The ridiculously good list of attending speakers
ZOMG! Srsly u guys! There hasn't been a large Flash conference in NYC...since...I don't know...2004? And that one pretty much sucked. But just look at the list of speakers! If you don't recognize the names, just trust me on this. They're are some really sharp people speaking about some great developments in the industry.

4. The Price is Right
Tickets right now are $299 (but lets just be real and say $300). In comparison to other conferences, this is CHEAP, especially for NYC standards.  And if you keep your ear in the community (Twitter, blogs, etc), you might even be able to find a coupon code!

I'd say these are my main reasons for anyone to attend the conference right now. I'm sure I'll come up with more and if I do, I'll update this post. Naturally, I plan on attending seeing as I live here and I hope to see you along with my other friends and colleagues here as well! It's gonna be a blast.

This was the first time I attended, so I'm not sure of the overall theme of previous years, but there was certainly a major focus on the social aspect of the industry. Just about everyone was talking about it. If they weren't specifically talking about it, then it was at least somehow mentioned.

One of my favorite sessions was When Worlds Collide: Human Centered Design Meets Agile Development. I know very little about either process, but it gave me some good insight into how the majority of designers and developers like to work. I felt it was interesting going into this panel without much knowledge of either process, and absolutely no experience implementing each process as well. Both are suited well for their given reasons, but they are fundamentally different in their approach. What I pulled away from this session was that its difficult to shoe-horn any given project into any specific process model, especially if you have a commandeering designer and/or engineer. It all comes down to providing respect to your counterparts. Designers and engineers must collaborate, communicate, and ultimately all be a part of the process from start to finish. This means that ego's have to be left behind and each side needs to think a little differently than normal. For instance, designers need to relax and not feel as if they have to understand everything about a user before trying to come up with a solution. Engineers on the other hand should focus on looking for opportunities rather than pointing out limitations. Personally, I believe this is the key to successful project.

There was also a lot of other good sessions during the time I was there. The most refreshing fact was that I didn't go to a single session that was focused on the Flash platform. The only Flash related thing that came up was when I was sitting in a session entitled Emerging Trends of Mobile Technology. I forget who it was exactly, but there was a panelist from Adobe (not listed on the description) who spoke a little bit about Adobe's effort to get the full Flash Player onto a bunch of devices by the end of 2009. Pretty exciting if you ask me.

Last but not least, the sponsored parties were a damn good time. Its a great time to meet random industry folks, drink a lot of tall boys, and run into the most influential people in your life. OK, maybe not the last one, but I did run into David Carson who I studied and took influence from for about three years during my college days as a graphic designer. That was pretty interesting. Wish I could have talked to him, but he was a bit distracted by something. Two of the parties I attended were at The Mohawk, a pretty rad venue/bar with all sorts of outdoor space and a free flowing bar. Highly recommend going there for some live music.

With any luck I'll be able to return next year. I really think its a great place to get in the know and see whats happening elsewhere in the digital community/industry. Oh, and thanks to Rokkan for sending me along with a few other coworkers.

Perhaps its difficult for people who don't develop web applications (actually write code) to understand that this is just an effort to standardize public API's across social networking services. I'm rather excited about the possibility of being able to develop an Actionscript library that can perform the same exact method calls (getPerson, getFriends, addActivity, etc.) and just have to specify the service to use (LinkedIn, Orkut, etc. ). At least thats how I'm envisioning all this.

I also find it funny that a lot of people are getting all anxious over the possibility of Facebook refusing to implement the standard. Facebook is certainly in its own little world. While its a pretty good example of a web application that offers a public data API, it still has a bit of a "pet project" feel to it and I don't feel as if the owner/creator is that concerned with adopting an API standard. Developers are already happily using their API with good success. Perhaps it will hurt them in the long run, but even if they become late adopters, its going to be a standard API, thus making it easy for developers to add Facebook into their existing OpenSocial standard apps.

In the end, I'm pretty stoked about this, but probably only because I'm a developer.

On top of this, we're presenting at FlashForward, Boston in September. Our presentation is entitled, "Designers vs. Developers: How to Avoid Fights on the Playground." As the name implies, it's going to be focusing on how Designers and Developers can work together better by understanding some helpful tips and tricks of each of the disciplines. Matt & I are originally from a design education, but as it turns out, we've both weaseled our ways into programming/development roles in our respective companies. As such, we constantly rack our brains on how the two different sides of the office can work together better, or how designers could learn the basics of programming easier.

We'll hopefully talk more about these things in the upcoming months, as we get closer to launch dates.