You're browsing the “Front End Engineering” category.

Installing software people didn’t request erodes trust. It’s especially repugnant when it hitches a ride with a security or version update. Marshall Kirkpatrick’s right: downloading software has to be opt-in, not opt-out.

As technologists, we want up to date users. Beyond the real user-safety issues, it frustratingly holds us back. The oldest browser is the lowest common denominator and holds us all back. But sneaking new software into the sacred realm of auto-updating flows is unwise. We cannot take advantage of users at the exact moment we want them to trust us blindly and reflexively.

Multiple Apple products are within arm’s reach. My first technology experience several decades ago was on an Apple product. Love ‘em, but they should know better.

I’m glad John wrote his post.

I’ve heard about various services that charge a flat rate to chop Photoshop (etc) files into clean (X)HTML and CSS, generally for a flat fee and quick turnaround. The topic came up today when a freelancing application developer buddy asked me about this type of service.

So this morning I asked my twitter followers (follow me!) which services they knew of. Here’s what came back (in a matter of minutes - gotta love twitter!):

• psd2html.com
• w3-markup.com
• xhtml-slice.com
• slicerus.com
• xhtmlit.com
• xhtmlized.com
• xhtmlgenius.com

Then @jasonw22 pointed out that Jonathan Snook (a hero of mine) has a list of about 20 such services, and just this week posted a review of his experience auditioning the psd2html service.

If you’ve used any of these services, I’d love to hear about your experiences in the comments below (and of other services you may know of or recommend).

I’ll report back on my friend’s experience.

(I must mention, in closing, that I’m skeptical of such services. I’ve spent the last several years of my career promoting the professionalism of frontend engineering, and so I have a twang of fear that these services are a step in the wrong direction. Then again, perhaps services such as these — if, in fact, the quality is there — prove that some aspects of “professional grade” web development are now par for the course. Jury’s still out.)

Congratulations to my friend and colleague Stoyan Stefanov for the publication of Yahoo!’s Latest Performance Breakthroughs after presenting them at the PHP Quebec Conference in Montreal last week. The 20 new tips bring to 34 the total performance tips his team at Yahoo! has published in the past two years.

Stoyan (who authors the phpied.com blog) is part of an established tradition of Yahoo! sharing performance research publicly and widely. Stoyan’s teammate Tenni Theurer concluded the official blog post announcing these data and findings by saying, “We share our findings so that others can join us in accelerating the user experience on the web.”

I agree. That’s why I was honored to help disperse their 14 Rules for Faster Web Sites in my presentation at the @Media conference in London last year.

And that’s why it was a special honor to write the foreward to Steve Souders’ High Performance Web Sites book for O’Reilly last year. (Steve used to head up the Performance team at Yahoo!.) In the foreward I tried to express why performance matters to professional frontend engineers:

Here is why it matters. As a frontend engineer, you hold a tremendous amount of power and responsibility. You’re the users’ last line of defense. The decisions you make directly shape their experience. I believe our number one job is to take care of them and to give them what they want—quickly. This book is a toolbox to create happy users (and bosses, too). Best of all, once you put these techniques in place—in most cases, a one-time tweak—you’ll be reaping the rewards far into the future.

Read more about Yahoo!’s Latest Performance Breakthroughs on the Yahoo! Developer Network site.

It’s just been confirmed and announced that I’ll be speaking in Taiwan at the Open Source Developers’ Conference on the 12th and 13th of April 2008, on the campus of the School Of Continuing Education, Chinese Culture University in Taipei. My talk will offer an insider’s tour of the YUI Library:

The YUI Library is an open-source, a la carte JavaScript library for building richly interactive Web apps using techniques such as DOM scripting, DHTML, and AJAX. This library, free for the world to use, is the exact same code that is used globally and at massive scale on scores of Yahoo! sites. In this session, Yahoo!’s Nate Koechley will talk (and answer questions) about the design and technical philosophies behind YUI. You’ll learn what the library can do for you, where it’s heading, why and how Yahoo! decided to open-source it, and how you can use it to provide an outstanding user experience for your visitors.

OSDC.TW 2008 時間

在經過最後確認之後，我們已經正式公佈 OSDC.TW 2008 的時間跟地點：

時間：2008/4/12-13 地點：中國文化大學推廣教育部博愛校區 - 大新館

Yesterday during our weekly YUI team staff meeting we headed outside to snap a year-end picture of the team. Here it is!

From Left: Satyen Desai, Georgiann Puckett, Nate Koechley, Lucas Pettinati, Adam Moore, Douglas Crockford, Thomas Sha (behind the sign), Luke Smith, Matt Sweeney, Jenny Donnelly, and Dav Glass. Not Pictured: Todd Kloots and Eric Miraglia.

(Photo credit: Eric Miraglia. The YUI Team, December 20, 2007 Originally uploaded by superfluity.)

Douglas Crockford has a plan for Fixing HTML. I think it makes sense. His proposal is a static document, but comments are collected on his related blog post.

In the comments you’ll see a few issues pop up (empties, quotes, get-bys), but after further reflection I think they are without merit.