Category Archives: Web Dev

Tyler School of Art

Over the weekend, while I was sleeping under the stars at a Lehigh Valley farm, the new Tyler School of Art website went live. It’s the first project I was handed when I walked in the door at Bluecadet, so I’m glad to see it finally see the light of day. I worked with a small team on this: Rebecca Smith and Rebecca Sherman handled project management, Kim Quinn oversaw design, and Putra Roeung did most of the day-to-day coding (with an occasional detour into some design work as well). I led development, setting our technical goals and stepping in here and there to untie tricky knots in the Drupal/JS/SASS front.

I took copious technical notes that may yet turn into more focused posts, but this particular one is a bit more philosophical. In the past I’ve always been struck by acute sadness whenever a long-term project finally goes live. Is there post-partum depression for designers and developers? In those moments I tended to see only the ways in which a project fell short of my standards. I would run my hand along the rough edges and wish: for more time, for another flash of inspiration. I would assume that everyone who viewed my work had x-ray vision, able to see inside the walls to the tangled mass of spit and duct tape holding the whole thing together. I will tell you that it’s a terrible way to feel.

As makers we can be hard on our peers, and even harder on ourselves. We soft-pedal what should be a triumphant shout, pre-emptively reducing so much sweat and effort into an offhand remark: “So I made a little thing…”. But that kind of perfectionism is no fun. So in this case I’m going to stop myself from going down that road—the site lives and breathes, and that’s reason enough to celebrate. I helped make something, and it feels good.

We Didn’t Even Bother with a Funeral

John Biggs wrote a short post on Flash’s quiet mobile sunset: “Hey, Guys, Remember When You Used to Care About Flash?”. This bit stuck with me:

Where is the outrage? Where are the flame wars? Why are there no open letters to Adobe? It’s because people have moved on and it’s actually kind of appalling to see. All that energy wasted. All that ill-placed anger.

I first saw Flash (not Flash Lite) running on a mobile phone around the Summer of 2009. I was still working at Domani, and Adobe had just dropped off a Palm Pre with Adobe Flash beta running on it. We huddled over the tiny screen and loaded up a few of our recent sites. We cheered as the first one slowly loaded. However, the novelty of seeing our work on a mobile device was quickly replaced by the sobering reality: most of the text and interactive elements were too small. Sites didn’t fit properly onscreen. And then the sites crashed, repeatedly.

That was about a year before Steve Jobs and Apple would publish their “Thoughts on Flash”, but I already got the sense that Flash on mobile was going to have a very tough road ahead. So I started dusting off my HTML, JS, and PHP skills. In 2010, a few months before my wife and I decided to move to Philadelphia, I interviewed for a “Director of Flash Technology” job at an agency. I sometimes wonder where I would be if that had panned out.

As for the very vocal outrage, outrage that’s notably absent now: I think a lot of it wasn’t even about Flash on mobile. I think it had more to do to the fact that mobile cast scrutiny on how we were using Flash on the desktop. Having to suddenly pivot away from your comfort zone is scary. So people got defensive, dug in, and created a divide. Suddenly Flash became this symbol of “open” technology, unfairly shut out of Apple’s platform.

The guys who were quiet? They were the ones who realized that Flash was still good for a great many things, but for mobile it was going to be native apps or open web technologies. So they put their heads down and went to work, picking up new skills or brushing up old ones. Meanwhile, some of their colleagues shook their fists at Apple and played the waiting game, promising that each new release on Android would finally bring the “full web experience”. It was late to arrive, and never delivered on the promise. So now comes the inevitable news, and everyone shrugs. The ones who got a head start are busy learning and growing elsewhere; the blowhards have probably just found another symbolic divide to rally their banners around.

Sublime Text 2: Remapping Key Bindings

While looking for a way to remap the keyboard shortcut for “Enter Full Screen” to “Replace All”, I kept running into a wall. Merely specifying the same keyboard shortcut didn’t work, as Sublime Text seemed to favor the default mapping. I stumbled onto this note, however, which illustrated how to unbind a keyboard shortcut:

{ "keys": ["alt+shift+left"], "command": "unbound" }

So I ended up unbinding the shortcut, and then remapped it:

{ "keys": ["super+ctrl+f"], "command": "unbound" },
{ "keys": ["super+ctrl+f"], "command": "replace_all", "args": {"close_panel": true},
     "context": [{"key": "panel", "operand": "replace"}, {"key": "panel_has_focus"}]
}