Being in IT for so many years has made me wear a lot of hats: Web dev on some days, a designer on others and a guy who has friends ask him how to do “simple” things that aren’t all that simple. So it behooved me to grab a ticket and go to the HTML5 Developer’s conference in San Francisco earlier this month.

Summary

The conference was packed — literally in some cases, as people were bumping shoulders taking notes during some talks, while others overflowed with people sitting on the floor — full of useful and informative sessions. My day was spent listening to best practices from those in the know and collectively sharing inside jokes about IE6, pirates, cats and how no one outside of the Web development world gives a rat’s ass about what Web developers, especially front-end developers, do. The overall tone of the conference seemed to be that HTML5 (which is a catch-all term that also implies ECMAScript, aka Javascript, and CSS3) is but one part of the equation. While HTML5 is important, knowing how to use it properly will only take you so far. A bad back end can’t be salvaged with a good front end, and a great back end can be ruined by a dysfunctional front-end experience. I wonder why hairbrained ideas, where one side is critically important while the other isn’t, take root. Front end and back end are equally important, because if both sides aren’t well thought out, you end up shipping half a product. I wonder why Web developers are not real developers, and why scripters writing in PHP aren’t real programmers? The problem is that once an idea takes hold after an initial impression, no one ever thinks about updating their information. Chris Heilmann of Mozilla made a point about using workarounds long after they are necessary. His point was that we developers are being too clever for our own good by using workarounds that are no longer needed and that effectively hold us and the Web back. He also made a great observation about how the glut of tools has led to an environment where tool count in resumes exceeds the importance of understanding the fundamental technologies. We have so many awesome ways to do things now that we are suffering from an awesome overload. Every week there's a new framework a pro must know, even though it will eventually be superseded and replaced. Heilmann's bottom line was “learn the fundamentals” and you will never be out of work. Knowing fundamentals was a point I thought everyone knew, and I heard it about audio some 20 years earlier from my advisor and one of my favorite professors, John Barsotti at SFSU. The thing is, coming into this conference, I was not very confident that my self-taught skills (particularly Javascript) were up to snuff with people that have a Computer Science degree. But by the end of it, I felt pretty good. Here were speakers telling people things that I had already figured out (with the help of my heavy emphasis on production communications classes) on my own.   [caption id="attachment_88646" align="alignleft" width="300"] Conference Credentials[/caption] The lectures were by people who “get it” — a talent that seems to be missing from the cash-fat tech world. Heilmann put it all into perspective saying, “My brother is a fireman. When he makes a mistake, people die. When we make a mistake, something is 5 pixels off.” Oddly enough, I was the only one laughing at the dark part of the joke (probably because I knew where he was going with the punch line). But everyone that was there did care about that metaphorical 5 pixels. Each talk emphasized working together, and using best practices. The hot trends may be flashes in the pan, but standards stay. After the conference I have come away with two things that are sticking with me: (1) I wish all the browser makers would agree on a standard for audio and video support instead of battling it out for the one that makes them the most money. Having competition is great when platforms are independent, but the Web is not independent. Whenever people talk about technological standards and how everyone has their horse in the race, I can’t help thinking: This is less like everyone putting their horse into the race, and more like everyone putting their own jockey on one horse. That horse can barely walk with five-plus rendering jockeys, even if each one is lighter and faster than the previous one. Standards would make my job (and countless other developers’ jobs) easier. Luckily, we can code around the problem, but still — having to store two 50-MB files instead of one blows. (2) Learning how to actually write the HTML and CSS using the proper syntax, and even some best practices, is easy, but layouts are still in the print age. Everyone still thinks of the Web screen like a piece of paper whose layout can’t be edited, and instead if they want a different view, they switch pieces of paper. The only use of animation is for small effects that add a bit of pizzazz or drop-down menus. If we only use dynamic boxes for menus we will never approach the finesse and feel of a native app.

Moovweb Remix Mobile Hackthon: Mobilize GitHub

Moovweb is having a “Remix Mobile Hackthon” contest from April 2 until May 1. The object is to make the best mobile version of at least two pages of GitHub for either iOS 6.1.2+/iPhone4+ (Retina Displays) or Android 4.0+. The instructions are simple, and can be found here. The short version is that you sign up for Moovweb, download their SDK, and make a project on Github. Mobilize two or more pages using their tritium scripting language (which looks very similar to JQuery in terms of composition and syntax). The more pages mobilized, the higher your completeness score. The rules are pretty standard: Entrants must be current U.S. residents, 18 years of age or older before the contest start date (April 2), and not affiliated with either Moovweb or the HTML5 Developer’s Conference. Complete rules are available here. Image:HTML5 Developer Conference