Yes, I am going. I got the green light from my employer today. Me and two of my co-workers are going to London.
It is going to be great to see speakers like Jesse James Garret, the guy who coined the term Ajax, in real life. So if you are going to @media, europes best (?) web developement conference, see you there...

As I thought that it was about time, I updated my cv.
I still have some things to do, I want to make it more readable with some smart usage of javascript.
Beware though, it is in dutch, one more thing I wanna do, translate to english...

As I may or may not have told you, I love jQuery for its simple syntax. Not that is suitable to replace common (heavy) tasks as striping big tables, because of the speed difference. I mean, dom scripting is still way faster than (to my knowledge) any library.
But it's simple syntax makes it suitable to let non javascript people use it.
As I am leaving a project half way, I have a lot of loose ends. But jQeury lets me leave people with some good building blocks to finish the work.
In this project I employ all the possibilities of css, including Adjacent Sibling Selectors even though they don't work in IE.
Here is where jQuery comes to the rescue, with one simple line of code we make IE behave

This is where jQuery shines, it let's people just do stuff.However, it is still a bit scary, putting guns in the hands of children. See this article by Peter-Paul Koch, where he collects and reviews quite a few good opinions.

• Dave Shea
• Roger Johanson
• Rachel Andrews

first of the speakers are introduced. (You can find more info about them on google.) They start with tips about how to start, a equalizing stylesheet is mentioned. Which is a good thing, you first create a level playing field by removing all of the browser styling. Then you pick either a template or a framework. And start with your content.

The speakers are not on the same line with multiple css files, all I can say is my personal opinion. If you have several 1000's lines of code you have to split up your files, in a common way. By making a base.css, a layout.css and several files for large sections of the site or application. An extra to it is that is a more easy way to remove legacy code.

They also provide some usefull tips about commenting. Such as comment (in xhtml) your closing div, and begin your comment with a common character, like = comment. That makes searching easier. The most important thing they said and what everyone knows is COMMENT a lot and good. After 6 months you cannot remember why you did certain things.

After that they tackle naming conventions and code order only to arrive at one conclusion. You have to be consistent...

A nice talk with a conceptual look on mobile web. Do not first look at the technical stuff, but first look at why you will be going mobile. Put the user first and look at what he/she needs.

I will post a follow up on this...

The follow up:

It was nice but not very new to me, but then again I made my first wap game in 1999, so the mobile has been my playing field for some time now. And no, I have not tested this site mobile and have no intentions doing so, thank you very much.

Conclusion, I like his designs and his writing better than his presentation, sorry to say.