This Is the Journal.
There are currently 799 entries in Unstoppable Robot Ninja.
Here are the most recent five.
The Last Five Entries:
These thoughts aren’t especially well-formed, and/as I haven’t had my coffee yet.
So with that disclaimer out of the way, I have to say I’m a bit disappointed to hear Opera’s news: namely, that they’re abandoning their browser’s Presto engine, and adopting WebKit/Chromium instead.
Other folks far, far smarter than I have already weighed in. And don’t get me wrong: I’ve had my fair share of gripes with various bugs in Chromium (especially recently), but it’s a fantastic piece of software; as a friend said recently, ten-years-ago-me would’ve killed to have browsers as fine as we do now.
But right now, what I’m most worried about is the lack of diversity: four rendering engines is not exactly a large number, and going to three is a significant shift, if not an outright loss. Additionally, I worry we’re already facing a rather “well, it works with
-webkit, so why worry about anything else?” mentality, which is something we’ll have to work harder to combat. Especially with an engine as fragmented as Webkit.
Of course, since the news is all of, like, minutes old, this is all speculation. Hell, it’s not even that: this is all just a pre-caffeine ramble, and not an especially well-formed one at that. I will say that Bruce’s take leaves me feeling hopeful. And I hope he’s right, and I’m wrong to be a bit disappointed. But right now, I know there’s one less (fantastic) rendering engine in active development, and that makes me a little sad.
I’ve always sucked at writing.
Not the words, mind you: those usually come easily. (When I remember to sit down and write them, that is; hellooooooo, sad and neglected blog.) It’s more the process of the thing, I guess. It’s a struggle for me to get ideas down quickly; I get intimidated by the promise of that final draft, of shipping, so I often feel every word needs to be perfect as soon as it’s typed.
(No, I’m not going to tell you how long it took to write this fucking blog entry.)
Anyway. So, yes: writing’s hard. But I’m learning how to make it easier. And, alongside a few friends, I’m working on something that might make it easier for you, too.
Last year, I had a long conversation with Mandy. She talked about this idea she had: an idea for a tool that would facilitate conversation, discussion, and, most importantly, iteration during the writing process. Not just an application, actually: more a set of features to support a workflow, one that would, if done right, make writing not just easier, but better.
She and Jason had already sketched out how it might work. Soon after, David joined our merry band, and turned our responsive prototypes a living, breathing application. And Rob joined our team recently, and has been, as Mandy said, effortlessly solving problems we once thought impossible.
I’m sad to say that due to a personal matter, I’ve had to bow out of speaking at this year’s Mobilism conference. You might have seen PPK’s announcement to that effect, and I’m definitely disappointed I’ll miss the event.
Because let’s be honest: my absence isn’t going to do a damned thing to diminish how amazing this conference is going to be. Seriously, look at this lineup. Look at it. Learning from the likes of Scott Jenson, Stephen Hay, Jake Archibald, Lyza Gardner, and Jason Grigsby is too good to be true, and in Amsterdam? And if you haven’t already, watch Jeremy Keith’s epic mobile browser panel from last year, a performance he’s repeating again in May.
Yeah okay I’m officially depressed all over again about missing it.
I’ve been working with The Boston Globe for the better part of this year on the design of a new site. I first made that announcement in Boston, on the stage of An Event Apart this past May, to a ballroom of very enthusiastic (and, I assumed from said enthusiasm, very local) designers and developers. Today, on the New Media Days stage in Copenhagen, I made another announcement to a room of designers and developers from the news media: that earlier today, the Globe launched onto its new online home.
Honestly, I got excited in December of last year, as Filament Group dropped me an email to chat about a project they were about to start working on. Now, I’ve admired Filament’s work since Dan and I met them over beers and pizza a few years ago. But when they approached me with the prospect of working with them to design a new, responsive home for the Globe? Well, it’s like I said: with folks like Todd, Patty, Scott, and Maggie among their ranks, there are some people and projects you simply can’t turn down. (That Mat
curmudgeonfellow has been contracting there as well. You try saying “no” to that guy.)
The Globe had also hired a local design firm called Upstatement, and they worked closely with Miranda Mulligan, the Globe’s adroit digital creative director, to establish the new site’s look. Filament’s Patty Toland has already provided a better write-up of the project than I ever could, but I’ll echo her excitement over the collaborative workflow Miranda cultivated between Upstatement, Filament, and myself. I can’t think of any project I’ve worked on that was nearly as fun as the months that followed, as they were a giddy blur of building, sketching, and thoughtful discussion. We tried to work as iteratively as possible, quickly moving from Tito and Mike’s goddamned exquisite mockups into responsive prototypes, in order to experience the design “live” in the various devices and browsers we were supporting. As Aarron Walter might say, we were letting the use of the site inform its design—vetting our early design assumptions with prototypes, which also allowed us to identify areas that needed further visual refinement.
The site you see today is the result of that more collaborative workflow. A process that occurred between two teams who, on a more traditional design project, might have never met, nor established the kind of rapport that ultimately shaped the final product. If you’ve read my book, the final chapter discusses this process in a bit more detail. Heck, if you’ve seen me speak this year, chances are good you’ve already heard first-hand how wonderful I think this more cyclical approach to design and development is.
And on that point: it’s been kind of a weird experience, talking publicly for the better part of this year about a site that hadn’t yet launched. I mean, I was—and still am—incredibly proud of the small contributions I made, of the talented team I collaborated with, but still: talking about a site that hasn’t launched yet? There’s some part of me that’s felt, well, odd about that. What if people’s expectations aren’t met? What if we can’t deliver? What if the Internet gets hit by an exploding unicorn and we somehow don’t finish the project because NO MORE INTERNET YOU GUYS.
(Also, it might be a teensy goddamned bit terrifying/mind-blowing to see the phrase “responsive web design” pop up in a mainstream news publication. I’m just saying.)
A few months ago, Mark Boulton said something on Twitter that really resonated with me, and helped the stress attacks abate: namely, that “design is the stuff around the end result.” Emphasis mine, but Mark reminded me that “design” is the means, not merely the end; the path we walk over the course of a project, the choices we make. And that’s a process that continues throughout the life of a site, even after launch. Because as with any site of this scale, there’s work still to be done. Some optimization is being done as we speak, both on the front- and back-end; some bugs are being tracked, isolated, and squashed; and as the Globe’s content producers become more familiar with the framework and start making bolder decisions, I’m sure the design will be refined to better meet their needs. And above all else, the Globe definitely wants your feedback.
And so, yes: while I’m impossibly proud of the new Globe site of today, I’m most excited about where it’ll be tomorrow. There are too many fine people on the Globe dev team to properly thank them all, but staffed by people like Dan, Jesse, Ian, Caz, Fran, and Adam, I know they’re primed to do great things. People like Michael Manning and Jennifer McNelis helped us chart paths through some challenging questions. And it’s worth mentioning that none of this would have been possible without Jeff Moriarty’s endorsement of a broadly accessible, responsive design; with a champion like that, we could do—and I think the Globe will continue to do—some truly exciting things.
There’ve been a healthy number of reviews already: Andy Boyle is tracking the ones he can find, and Joshua Benton at the Nieman Journalism Lab wrote up a few more business-minded thoughts and observations. More will follow, I’m sure. Some will (I hope!) see the Globe’s new site as a referendum for the merits of a responsive design; others will find plenty to critique, and justify a more device-specific way of designing for the web.
Me, I think the answer’s inevitably somewhere in the middle. But honestly, the response I’m most looking forward to reading is yours: what you see online at bostonglobe.com is the result of a particular process, tailored to the needs of one project, one audience. There’s much we’ve done that could easily be approached from a different tack, or executed in another, perhaps better, way. And if you do happen to stumble upon that approach, that alternate solution, I really hope you’ll write about it, and share it with the rest of us.
In the meantime, I’ll be exploring the Globe site, hopefully alongside the rest of you. So much of it’s new to me, and I really can’t wait to see where it goes next.