Believe it or not, those are not the words I’d want to be introduced by. Every week I see a new article about the secret(s) of innovation. And then articles dissecting the word, suggesting better words, lauding innovation, deploring it. At the least, it’s fatiguing. But often I think it’s just barking up the wrong tree.
Don’t get me wrong: I find nothing categorically wrong with innovation. How could I, right? But as a designer, 90% of the time I’d rather do something really damn well than do something that’s innovative. I like much of Bela Fleck’s music, but I hope we’re not celebrating the man because he can make pitch-perfect quail calls with his banjo or because he’s sure to be the all-time best-selling heavy metal banjo crossover artist of all time. Innovative (if a bit hyperbolic), but not necessarily great.
There’s nothing innovative about any of the design I do, save for (maybe) a CSS hack developed as a means to an end now and then, but I can’t see why there needs to be. I’m in the business of communicating content visually and interactively. I respect the designers who not only push the craft forward through excellence in execution, but actually push the medium forward through innovation. Maybe the iPad (e.g.) will really enable us to better communicate content. I’m not denouncing innovation, but if no one ever calls me “innovative” I’ll be totally okay, as long as someone calls me “really good.”
When I write CSS, I maintain a general habit of respecting box-model discrepancies, meaning I don’t apply border, padding, or margin to an element on an axis for which I’ve specified a fixed dimension. One of my go-to hacks is to use text-indent to simulate padding-left when there aren’t multiple lines of text. (I also use line-height to simulate padding-top and -bottom.) So I can cover top, bottom, and left in most cases, but not right. Now I’ve hit upon a way to simulate padding-right (again, when I only need that padding on one line of text).…
In my new job I recently discovered what seems to be a bug in Firefox 3.5: when there is a link (or anything else to which an outline could apply, i.e., any element with an :active state or a tabindex) that is floated (i.e. float: left or float: right) inside a container with overflow set to auto, the outline on that link will take up space, contrary to the W3C spec. This means that such a link, if it fills the container in either the X or Y dimension, will cause scrollbars to appear when it is active (tabbed to or pressed).…
No long explanation about why I haven’t posted in a while. If you’re still reading, you want content, not apologies. But a short explanation: I took a new job (full-time, in an office) and moved to Seattle. That means that twelve8 creative is now based in Seattle, not Chicago!…
A while ago, I was directed to this prototype for the mozilla.org redesign, notable particularly for it’s use of an intelligent, fluid grid. I bookmarked it within a folder I keep for quick design inspiration, since there are several aspects of the design that I think are pretty great. Looking at it again the other day, I discovered a clever bit of CSS coding.…