Projects – Thoughts From Erichttp://meyerweb.com/eric/thoughts
Things that Eric A. Meyer, CSS expert, writes about on his personal Web site; it's largely Web standards and Web technology, but also various bits of culture, politics, personal observations, and other miscellaneous stuffThu, 08 Dec 2016 19:13:33 +0000en-UShourly134146138Name Suggestionhttp://meyerweb.com/eric/thoughts/2016/05/06/name-suggestion/
http://meyerweb.com/eric/thoughts/2016/05/06/name-suggestion/#commentsFri, 06 May 2016 19:58:06 +0000http://meyerweb.com/eric/thoughts/?p=3623I’ve started playing an occasional game with my iPhone, where I type in a word to start a message, and then repeatedly accept whatever autocorrect suggests as the next word. If I’ve understood the terms correctly, I’m manually accepting iOS’s Markov chain output.

I’m inclined to post the results to a Twitter account, sort of like I did for Excuse of the Day, but I’m stuck on the most prosaic of roadblocks: I’m having trouble thinking of a good name for it. (Here, ‘autosuggest’ will not help me.) Anyone have a winning name they’re willing to contribute? Full credit to the winner in the Twitter bio, not to mention here, plus a percentage of the multi-million-dollar royalties from the inevitable book and movie deals.

Anil Dash was kind enough to write a wonderful foreword for the book, in which he perfectly describes the background we were working against:

Two billion people now have some kind of access to internet technologies, and almost all of them are spending more and more time with their thumbs flicking across their phones. And the technology they’re using has a real impact on their lives. They don’t use an app to “share photos”; they use it to maintain a relationship with distant family. They don’t need to do “online banking”; they need to lend a friend money to help them out of a jam. Nobody wants to learn a complicated set of privacy controls; they just want to be able to express themselves without antagonizing bosses or in-laws.

Our thesis, against that, was to say, “As personal and digital lives become closer and effectively merge, the things we design will have to work harder and harder to deal with real people in all their messy complexity. How can we start people thinking about this, and what tools can we give them?” That’s what we strove to create, and now you can judge for yourself whether we succeeded.

I’ll be honest: we were pretty scared as we wrote it. This is not a topic area that’s gotten a ton of attention, and in a lot of ways we were breaking new ground—but, at the same time, we were very aware that there was existing research and knowledge in related areas, so we wanted to be sure we were inclusive or, and respectful of, that work. We talked to a lot of people in a variety of disciplines, trying to make sure we brought in information that would help the reader and not flying in the face of things that were already known.

So you can imagine our relief and gratitude as we’ve heard glowing reactions from people who read preview drafts—among them Kim Goodwin, Indi Young, Sara Soueidan, Caren Litherland, and Karen McGrane. Paul Ford said, “Anyone who aspires to build global products that people love should read this book now,” and Kate Kiefer Lee said, “It will be required reading on my team.”

You might think cover blurbs like those are pure marketing fluff, and maybe in some genres they are. For us, they serve double duty: to let you know that people who know what they’re talking about believe we know what we’re talking about, and also to let us know that. There were days we weren’t entirely certain.

To be clear, this isn’t a book about forever treating people with kid gloves. We say “compassion isn’t coddling”, and that’s absolutely the case. An error message still needs to convey the error; an account lockout still needs to keep the account locked. But how we convey errors or lockouts, and how we make people aware of the possible ramifications of their actions, is critical. Just as there are good ways and bad ways to commiserate with a grieving friend or handle a difficult work situation, there are good ways and bad ways to approach people in our designs.

As I said before, we need to deal with real people, in all their messy complexity. We hope Design for Real Life is the start of a whole new conversation within our field, one that will teach Sara and me just as much as anyone else about how we can be more thoughtful and humane in what we create.

]]>http://meyerweb.com/eric/thoughts/2016/03/08/design-for-real-life-now-available/feed/13587Local Ipsumhttp://meyerweb.com/eric/thoughts/2015/11/23/local-ipsum/
http://meyerweb.com/eric/thoughts/2015/11/23/local-ipsum/#commentsMon, 23 Nov 2015 18:59:46 +0000http://meyerweb.com/eric/thoughts/?p=3464Throughout 2015, a few people who’ve seen me present “Designing for Crisis” at An Event Apart have noticed that, on the slides where I have filler text, it’s a localized variant. In Washington, DC, for example, one section started out:

This was a product of some simple PHP I’d originally written to generate Cleveland-themed filler text a year or so back, which you can find at localipsum.meyerweb.com, and which I’d expanded upon to let me generate text for my presentations at AEA. The name comes from the original idea I had, which was to provide a list of cities/regions/whatever, so that users could pick one and generate some filler text. That never quite came together. I had a semi-working version once, but the UI was horrible and the file management was worse and I got discouraged and rolled back to what you see now.

I kept telling myself that I’d get back to it, do the city-selection thing right, polish it nicely, and then finally release the source. I’ve told myself that all year, as I manually swapped in city information to generate the filler text for each of my talks. Now I’ve finally admitted to myself that it isn’t going to happen, so: here’s the source. I chose a pretty permissive license—BSD-ISC, if I recall correctly—so feel free to make use of it for your own filler text. I’ll be happy to accept pull requests with improvements, but not package-management or complete MVC restructuring. Sorry.

I know, it’s a goofy little thing and the code is probably pants, but I kinda like it and figure maybe someone out there will too. If nothing else, we can look for a few laughs in the output and maybe—just maybe—learn a little something about ourselves along the way.

(P.S. Speaking of “Designing for Crisis”, look for a post about that, and more specifically video of it, in the next few weeks.)

]]>http://meyerweb.com/eric/thoughts/2015/11/23/local-ipsum/feed/13464Rebecca’s Boardwalkhttp://meyerweb.com/eric/thoughts/2015/10/15/rebeccas-boardwalk/
http://meyerweb.com/eric/thoughts/2015/10/15/rebeccas-boardwalk/#respondThu, 15 Oct 2015 18:18:05 +0000http://meyerweb.com/eric/thoughts/?p=3391Rebecca’s Boardwalk, a fundraiser in support of Rebecca’s Gift.]]>One month from today is the first-ever Rebecca’s Boardwalk, a fundraiser in support of Rebecca’s Gift. It’s a family-friendly afternoon of carnival games with actual prizes to be won, a facepaint and temporary tattoo booth (many thanks to Tattly for their generous support!), indoor mini-golf and bounce houses, boardwalk food, and a pretty great silent auction. We’ll have everything from gift-card grab bags to artisanal meat parties to signed shooting scripts from The Walking Dead up for bid!

All of the proceeds will go to fund the mission of Rebecca’s Gift, which is to provide healing family vacations after the death of a child. The organization has already raised enough to assist at least two families in 2016. We’d very much appreciate your support in helping us lend a helping hand to more families in desperate need of time to reconnect, rebuild, and relax. It’s one of the very few organizations we know of that supports families after a child’s death, as opposed to before. This is something I touched on in a piece I wrote for Natural Papa back in September, in conjunction with St. Baldrick’s. It’s something Kat and our friend Karla are determined to do something about, and I’m honored to support their efforts.

I very much hope you can join us for Rebecca’s Boardwalk, or if not, support the event via a sponsorship. Rebecca loved travel and boardwalks in particular, and we can’t think of a better way to celebrate her life while striving to help others heal as best we can.

(Side note for the web folks in the audience: the Rebecca’s Gift site in general, and the event page in particular, makes use of flexbox for simple layout. Just in case you were looking for a public deployment example.)

]]>http://meyerweb.com/eric/thoughts/2015/10/15/rebeccas-boardwalk/feed/03391Finding My Wayhttp://meyerweb.com/eric/thoughts/2014/12/19/finding-my-way/
http://meyerweb.com/eric/thoughts/2014/12/19/finding-my-way/#commentsFri, 19 Dec 2014 18:49:37 +0000http://meyerweb.com/eric/thoughts/?p=3127With presentations of “Designing for Crisis” at AEA Orlando and World Usability Day Cleveland now behind me, I’m getting into the process of reviewing and refining the talk for 2015. This will be my talk at An Event Apart all throughout this year, making me one of the rare AEA speakers who won’t have a brand-new talk in 2015. (We’ll have a mix of new and familiar faces, as we always try to do, and they’ll all be bringing new material to the stage.)

Even “Designing for Crisis” will have some new aspects to it, as I discover ways to strengthen it and loop in some new thoughts and discoveries. As an example, I just recently had a great chat with Amy Cueva, who gave me some really sharp insights into how I can share the message even more effectively. I expect that kind of iterative improvement to continue throughout the year, given how new the topic is to me, and possibly to everyone. It’s been something of a surprise to have many people tell me it’s caused them to see their own work in a whole new light—even people working in fields where you might think they would already be on top of this. I’m really excited to bring this talk to people at AEA, and elsewhere as opportunities arise. I hope it will do some good in the world.

In parallel with that ongoing effort, I’m getting back to writing more than just the occasional blog post. I’ve restarted work on the fourth edition of CSS: The Definitive Guide—details on that will be forthcoming just after the holidays. I’m also starting to write down some of the thoughts and approaches in “Designing for Crisis”, as well as some nascent thoughts on network effects, responsibility, community, and guidance. I’m also trying to teach myself git so I can push out public repositories of my CSS tests and some bits of code I’d like to release into the wild, but honestly that’s pretty slow going, because it’s always a fifth or sixth priority behind my family, working on AEA, refining and rehearsing the new talk, and writing.

(“Bits of code”. SEE WHAT I DID THERE?)

Given everything that’s coming together, I really am looking forward to 2015 and a return to speaking and writing. For painfully obvious reasons, I was pretty out of the loop for nearly all of 2014, not to mention the last half of 2013. I tried to stay up to date, but it’s one thing to be in the middle of things, and quite another to observe things from a distance. (The mosh pit never looks like it feels, you know?) So in addition to all the other stuff, I’m working overtime to catch up, and that’s where I could really use some help from the community.

So, tell me: what did I miss? What’s emerging that I should be (or should already have been) paying attention to, and what am I already behind the curve on? What has you excited, and what sounds so awesome that you’re hungering to know more about it? And maybe most important of all, where should I be going to get caught up?

All input welcome, whether here in the comments, or out there on les médias sociaux. And thank you!

]]>http://meyerweb.com/eric/thoughts/2014/12/19/finding-my-way/feed/193127Gravity Wars Reduxhttp://meyerweb.com/eric/thoughts/2014/09/25/gravity-wars-redux/
http://meyerweb.com/eric/thoughts/2014/09/25/gravity-wars-redux/#commentsThu, 25 Sep 2014 15:07:22 +0000http://meyerweb.com/eric/thoughts/?p=3059Over the past few weeks, I’ve been writing a remake of/homage to a game I last played somewhere around 1990: Gravity Wars. I gave this personal project a few hours here and there each day, or more usually each evening, slowly resurrecting a little piece of my past and putting my own spin on it. You can check it out for yourself, if you like: Gravity Wars Redux.

There are a few things I changed from the version I played all those years ago, besides the change of colors. First of all, instead of taking turns, in my version the ships fire simultaneously, meaning a no-survivors tie is possible. Second, the shot preview paths weren’t part of the original game. Third, the “Gravimetric display” wasn’t a thing in the original game either. That and the shot previews are leftovers from my development testing that I decided to keep around, either because I thought they added something to the game or because I just liked them too much to dump.

In fact, most of the code in there is accreted leftovers from the experimentation and development process. Looking at it now, I can see all the things I should have done. It just got to a point, as with most coding projects, where I could add another scoop or two of spaghetti to the existing mound and ship it, or I could start over and try to make the lasagna properly this time. I decided to ship it.

I have to admit the point of all this wasn’t actually to recreate Gravity Wars, as much as I like the game and am glad to have a working copy of it. It was instead to teach myself about the canvas API, and also to try to get a handle on some JS features that have never quite made sense to me. I think I did okay on the both fronts, in my own idiosyncratic way.

At this point in a JS-related post, I usually throw in a disclaimer about being a JS newb whose code should never be inspected by anybody. That’s probably still true, but I know I’ve advanced quite a bit from where I was, which pleases me. I can see that not just in that the code I’m publishing today, which is convoluted and clumsy but still better than what I’ve written in the past. I can also tell I’ve gotten better simply because I can see better approaches, as a result of what I learned along the way.

This may be where I end the project, or I may go back and take another crack at making lasagna. We’ll see. The carrot for me in doing that is it would let me add some other fun features and useful improvements pretty cheaply, not to mention I could fix some things that aren’t quite what they should be (like the placement of planets and ships, which should be a little less random). The stick is of course having to rewrite code I already wrote. I mean, lasagna is nice and all, but I like spaghetti too.

]]>http://meyerweb.com/eric/thoughts/2014/09/25/gravity-wars-redux/feed/73059Catching Up: TWB #2 and #3http://meyerweb.com/eric/thoughts/2012/10/10/catching-up-twb-2-and-3/
http://meyerweb.com/eric/thoughts/2012/10/10/catching-up-twb-2-and-3/#respondWed, 10 Oct 2012 19:05:57 +0000http://meyerweb.com/eric/thoughts/?p=2022I’ve been a little bit remiss in keeping up with The Web Behind. I think that’s irony? Or maybe it’s just a bummer.

Anyway, the second episode, starring Steve Champeon, was recorded and released last week. Hear about SGML and HTML, progressive enhamcement, the inside and little-known story of the WaSP’s success, and more. I learned at least one thing I had never heard before, and Steve’s just a fun guy to talk to regardless of topic, so hopefully you’ll find it as interesting as I did.

Next week, we’ll be recording our third guest, Dave Shea, on the afternoon of Wednesday, October 17th (a week from today!). In addition to being a pretty darned fantastic designer, Dave is of course the mastermind behind the groundbreaking CSS Zen Garden. We’ll spend our time talking about that and other products of Dave’s brilliance, like CSS Sprites and Chalkwork Icons, as well as find out what he’s been doing of late. Jen and I hope you’ll join us!

]]>http://meyerweb.com/eric/thoughts/2012/10/10/catching-up-twb-2-and-3/feed/02022Pricing ‘CSS:The Definitive Guide’http://meyerweb.com/eric/thoughts/2012/10/03/pricing-csstdg4e/
http://meyerweb.com/eric/thoughts/2012/10/03/pricing-csstdg4e/#commentsWed, 03 Oct 2012 15:17:38 +0000http://meyerweb.com/eric/thoughts/?p=2010CSS: The Definitive Guide, Fourth Edition":http://meyerweb.com/eric/thoughts/2012/10/01/csstdg4e/, I left out the question of how pricing will work. There are two components to the answer.]]>When I announced the serial publication of CSS: The Definitive Guide, Fourth Edition, I failed to address the question how pricing will work. Well, more decided to break it out into its own post, really. As it turns out, there are two components to the answer.

First component is the pricing of the pre-books. Roughly speaking, each pre-book will be priced according to its length. The assumed base for the electronic version is $2.99, and $7.99 for the print version, with significantly longer pre-books (say, one where two chapters are combined) priced somewhat higher. How much higher depends on the length. It’s possible that prices will drift a bit over time as production or printing costs change, but there’s no way to guarantee that. We’re basically pricing them as they come out.

At the end of the process, when all the chapters are written and bundled into an omnibus book edition, there will be discounts tied to the chapters you’ve already purchased. The more chapters you bought ahead, the deeper the discount. If you bought the pre-books direct from O’Reilly, then you’ll automatically get a discount code tailored to the number of pre-book you’ve already bought. If you bought them elsewhere, then O’Reilly’s customer service will work to create a comparable discount, though that will obviously be a slower process.

The second component is: how much will the codes cut the price of the final, complete book? That I cannot say. The reason is that I don’t know (nor does anyone) what minimum price O’Reilly will need to charge to cover its costs while taking into account the money already paid. I’m hopeful that if you bought all of the pre-books, then the electronic version of the final book will be very close to free, but again, we have to see where things stand once we reach that point. It might be that the production costs of the complete book mean that it’s still a couple of bucks even at the deepest discount, but we’ll see! One of the exciting things about this experiment is that even my editor and I don’t know exactly how it will all turn out. We really are forging a new trail here, one that I hope will benefit other authors—and, by direct extension, readers—in the future.

]]>http://meyerweb.com/eric/thoughts/2012/10/03/pricing-csstdg4e/feed/12010‘CSS: The Definitive Guide’, Fourth Editionhttp://meyerweb.com/eric/thoughts/2012/10/01/csstdg4e/
http://meyerweb.com/eric/thoughts/2012/10/01/csstdg4e/#commentsMon, 01 Oct 2012 17:42:42 +0000http://meyerweb.com/eric/thoughts/?p=1995CSS: The Definitive Guide, Fourth Edition, is being released one piece at a time.]]>I’m really excited to announce that CSS: The Definitive Guide, Fourth Edition, is being released one piece at a time.

As announced last week on the O’Reilly Tools of Change for Publishing blog, the next edition of CSS:TDG will be released chapter by chapter. As each one is finished, it will go into production right away instead of waiting for the entire omnibus book to be completed. You’ll be able to get each standalone as an e-book, a print-on-demand paper copy, or even as both if that’s how you roll. I’ve taken to calling these “pre-books”, which I hope isn’t too confusing or inaccurate.

There are a lot of advantages to this, which I wrote about in some detail for the TOC post. Boiled down, they are: accuracy, agility, and à la carte. If you have the e-book version, then updates can be downloaded for free as errata are corrected or rewrites are triggered by changes to CSS itself. And, of course, you can only buy the pre-books that interest you, if you don’t feel like you need the whole thing.

I should clarify that not every pre-book is a single chapter; occasionally, more than one chapter of the final product will be bundled together into a single pre-book. For example, Selectors, Specificity, and the Cascade is actually chapters 2 and 3 of the final book combined. It just made no sense to sell them separately, so we didn’t. “Values, Units, and Colors”. on the other hand, is Chapter 4 all by itself. (So if anyone was wondering about the pricing differences between those two pre-books, there’s your explanation.)

If you want to see what the e-book versions are like, CSS and Documents (otherwise known as Chapter 1) has been given the low, low price of $0.00. Give it a whirl, see if you like the way the pre-books work as bits.

My current plan is to work through the chapters sequentially, but I’m always willing to depart from that plan if it seems like a good idea. What amuses me about all this is the way the writing of CSS: The Definitive Guide has come to mirror CSS itself—split up into modules that can be tackled independently of the others, and eventually collected into a snapshot tome that reflects a point in time instead of an overarching version number.

Every pre-book is a significantly updated version of their third-edition counterparts, though of course a great deal of material has stayed the same. In some cases I rewrote or rearranged existing sections for greater clarity, and in all but “CSS and Documents” I’ve added a fair amount of new material. I think they’re just as useful today as the older editions were in their day, and I hope you’ll agree.

Just to reiterate, these are the three pre-books currently available:

CSS and Documents (free) — the basics of CSS and how it’s associated with HTML, covering things like link and style as well as obscure topics like HTTP header linking

Values, Units, and Colors — fairly up to date, including HSL/HSLa/RGBa and the full run of X11-based keywords, and also the newest units except for the very, very latest—and as they firm up and gain support, we’ll add them into an update!

As future pre-books come out, I’ll definitely announce them here and in the usual social spaces. I really think this is a good move for the book and the topic, and I’m very excited to explore this method of publishing with O’Reilly!

]]>http://meyerweb.com/eric/thoughts/2012/10/01/csstdg4e/feed/281995John Allsopp to Inaugurate ‘The Web Behind’http://meyerweb.com/eric/thoughts/2012/09/18/john-allsopp-to-inaugurate-the-web-behind/
http://meyerweb.com/eric/thoughts/2012/09/18/john-allsopp-to-inaugurate-the-web-behind/#commentsTue, 18 Sep 2012 21:08:23 +0000http://meyerweb.com/eric/thoughts/?p=1978John Allsopp.]]>Jen Simmons and I are very pleased to announce that our first guest on The Web Behind will be none other than John Allsopp.

Hailing from Sydney, Australia, John by himself has seen and done more on the web than most web teams put together. First encountering the web in the early 1990s, he built one of the very first CSS tools, Style Master, and a number of other web development tools; published a wealth of information like support charts and free courses; wrote the deeply insightful and far-seeing article “A Dao of Web Design”; influenced the course of the Web Standards Project; and founded a successful international conference series that continues to this day.

We’re incredibly excited to have John as our inaugural guest, and hope you’ll join us for the live recording this Thursday, September 20th at 6pm Eastern/3pm Pacific. That’s also Friday, September 21st at 8am Sydney time, and 2200 UTC if you want to calculate your own local offsets. The time zone dance is the reason we’re recording the first show at that particular time. Moving forward, the plan is to record on Wednesdays, usually mid-afternoon (US Eastern) but sometimes in the morning—again, depending on the time zones of our guests.

Be able to say you were there when it all started: please join us for the live recording, and subscribe to get the finished podcasts as they’re released. We already have some great guests lined up for subsequent shows—more on that as we firm up dates and times—and some interesting plans for the future. We really hope you’ll be there with us!

]]>http://meyerweb.com/eric/thoughts/2012/09/18/john-allsopp-to-inaugurate-the-web-behind/feed/11978The Web Behindhttp://meyerweb.com/eric/thoughts/2012/09/11/the-web-behind/
http://meyerweb.com/eric/thoughts/2012/09/11/the-web-behind/#commentsTue, 11 Sep 2012 20:47:37 +0000http://meyerweb.com/eric/thoughts/?p=1948Whenever I meet a new person and we get to talking about our personal lives, one of the things that seems to surprise people the most, besides the fact that I live in Cleveland and not in New York City or San Francisco, is that I have a Bachelor’s of Art in History. The closest I came to Computer Science was a minor concentration in Artifical Intelligence, and in all honesty it was more of a philosophical study.

To me, history is vital. As a species, we’ve made a plethora of mistakes and done myriad things right, and the record (and outcomes) of those successes and failures can tell us a great deal about how we got to where we are as well as where we might go. (Also, from a narrative standpoint, history is the greatest and most authentic story we’ve ever told—even the parts that are untrue.) The combination of that interest and my ongoing passion for the web is what led me to join the W3C’s recently formed Web History Community Group, where efforts to preserve (digital) historical artifacts are slowly coalescing.

But even more importantly, it’s what has led me to establish a new web history podcast in association with Jen Simmons of The Web Ahead. The goal of this podcast, which is a subset of The Web Ahead, is to interview people who made the web today possible. The guests will be authors, programmers, designers, vendors, toolmakers, hobbyists, academics: some whose names you’ll instantly recognize, and others who you’ve never heard of even though they helped shape everything we do. We want to bring you their stories, get their insights and perspectives, and find out what they’ve been doing of late. The Mac community has folklore.org; I hope that this podcast will help start to build an similar archive for the web. You can hear us talk about it a bit on The Web Ahead #34, where we announce our first guest as well as the date and time for our first show! (Semi-spoiler: it’s next week.)

Jen and I have took to calling this project The Web Behind in our emails, and the name stuck. It really is a subset of The Web Ahead, so if you’re already subscribed to The Web Ahead, then episodes of The Web Behind will come to you automatically! If not, and you’re interested, then please subscribe! We already have some great guests lined up, and will announce the first few very soon.

I haven’t been this excited about a new project in quite some time, so I very much hope you’ll join Jen and me (and be patient as I relearn my radio chops) for a look back that will help to illuminate both our present and our future.

]]>http://meyerweb.com/eric/thoughts/2012/09/11/the-web-behind/feed/81948An Event Apart 2013http://meyerweb.com/eric/thoughts/2012/09/10/an-event-apart-2013/
http://meyerweb.com/eric/thoughts/2012/09/10/an-event-apart-2013/#commentsMon, 10 Sep 2012 17:25:13 +0000http://meyerweb.com/eric/thoughts/?p=1959It’s a little bit hard to comprehend just how incredible a year we’ve had at An Event Apart. Our colleagues in the audience as well as on stage have been consistently sharp, engaging, and all-around amazing, and I don’t think Jeffrey and I could thank everyone enough even if we were given three lifetimes to tackle the project. With all seven shows this year selling out (some months in advance), we’ve taken the next step and have scheduled eight shows next year, a figure that occasionally causes me to go a little short of breath at the sheer wonder of it all. I think back on the hundred-odd people who filled the room at our very first event, tucked away in the upper back corner of Philadelphia’s Franklin Institute back in 2005, and can scarcely believe how far we’ve come.

If you’re inclined to join us in 2013, and I really hope you are, here are the cities and dates:

As was the case this year, all eight of 2013’s shows will feature a mix of new and familiar speakers presenting all-new talks shedding light on old problems and new ideas. Thus not every show’s lineup is yet complete: while we already have some speakers confirmed and announced for every event, we’re leaving the later shows in the year open so we can add fresh speakers and timely content.

Since all eight shows went on sale last month we’ve already had a bunch of people register, so you should definitely get those approval processes moving now if you want to avoid being shut out. We had lengthy waiting lists at every 2012 show, and there were very few cancellations. It never feels good to turn people away, but the venues’ capacities are what they are!

Being a part of An event Apart has been an amazing experience for me and for so many people, and our overriding goal is to make 2013 even better. I hope you’ll join us!

If you really want the TL;DR version, the results are largely the same as they’ve been in the past. The gender ratio, for example, is still in the vicinity of 5-to-1 male-to-female, with half a percent answering Other (a new option in the 2011 survey). Most respondents are in the age range 19-44 and live in the United States. And so on. That might sound like I’m bored by the results, but their very consistency even as the number of respondents has dropped over five years fascinates me.

It did take quite a while to publish the results. I feel personally very bad about the delay, because I run the numbers and it just took me a long time to get them run. Partly, I admit, I put it off because some of the numbers in previous years were a royal pain to generate, thanks in part to the way the data is formatted and in part because of the fine slicing that was done. This was finally addressed through various means, and now the report is done. I can’t thank Sara Wachter-Boettcher enough for her keen editing eye and firm strategic oversight, not to mention writing all the commentary text to accompany the charts. If not for her, the report might still not be done. And of course without the unwavering support and dedication of Jeffrey Zeldman, the survey might not have existed at all.

So we’ve done this five times, and the results are consistent. What now? There is much to discuss, and the answers aren’t yet clear; but I do know that this project brings me more professional pride than almost anything I’ve ever done. It tells us a lot about ourselves—and in a profession that is often characterized by single-person “web teams” and distributed offices, one which may never have a certification process or other form of registry, that’s something valuable. Thank you for helping us see ourselves a little bit more clearly.

]]>http://meyerweb.com/eric/thoughts/2012/09/06/results-from-the-survey-2011/feed/51943Cicadientshttp://meyerweb.com/eric/thoughts/2012/06/22/cicadients/
http://meyerweb.com/eric/thoughts/2012/06/22/cicadients/#commentsFri, 22 Jun 2012 20:47:29 +0000http://meyerweb.com/eric/thoughts/?p=1926The Cicada Principle” since it was first published. After wandering through a CSS gradients gallery or two back in April, it occurred to me that it ought to be simple to merge the two things.]]>I’ve been a fan of “The Cicada Principle” since it was first published. After wandering through a CSS gradients gallery or two back in April, it occurred to me that it ought to be simple to merge the two things. So I did: thus was born “Cicadients”. It took me until now to actually blog about it because, well, you know, things were, hey, what’s that weird thing over there?

What?

As a recap, the Cicada Principle states that if you pick a few simple patterns that repeat at prime-number intervals, you can create complicated patterns that only repeat at intervals that are the product of the individual intervals. For example, if you have patterns that repeat every 3, 5, and 7 pixels (respectively), the combination of the three will repeat every 3×5×7 pixels, which is to say every 105 pixels. Bump up the intervals, and you get some truly staggering numbers. For example, shift up to 7, 11, and 13 pixels and their combination repeat every 1,001 pixels; combining 11, 13, and 17 gets you 2,431; combining 13, 17, and 23 yields 5,083.

The examples presented in the original article use semi-opaque PNGs to achieve this effect. All I did was replace their images with images of my own; to wit, CSS gradients. (Yes, gradients are images, every bit as much as any PNG. They’re just described differently.) In doing so, I not only reduced server hits, but I also saved a fair number of bytes. In the first case, I did so while achieving pixel-perfect fidelity to the original. In the second case, I didn’t make it exactly the same as the original, but I got fairly close in 0.63KB (2.81KB with prefixes). I could probably get closer to the original with a little more effort—a couple of my gradients are a little too smeary—but that will probably wait a while, if I ever get to it at all. But, again, the final result is a kilobyte or two; the original example was 23KB plus extra server hits.

That was the real reason for my efforts, aside from the simple pleasure of doing it: to find out how much more efficient a gradient could be than a raster image in appropriate situations. I had expected some savings with gradients, but I was frankly astounded by how much was saved. You can do a lot more with gradients than sunset backgrounds and lickable button highlights.

Of course, gradients are not right for every situation: the third example in “The Cicada Principle”, for example, should only be done with gradients as an example of how not to do it. Possibly also as a public declaration of deep masochistic tendencies. Either way, you’d probably crash browsers, and that’s currently the job of radial gradients.

I’ll be very interested to see if people come up with their own cicadient examples. If you do, let us know about them in the comments!

To take those two things in reverse, I got word from my editor that color is definitely an option for the book, though the exact form it will take is not 100% certain. The options range from an insert of color plates to printing color on a per-page as-needed basis, and it’s hard right now to know what will make the most sense for the book and its price. We’re hoping for the per-page approach, but it will depend on just how fast color prices plunge in the near(ish) future and what the book requires. The glorious, glorious upshot is that I can abandon all thought of grayscale requirements and only concentrate on avoiding light yellows, which I guess print badly.

Getting HSL from RGB — a look at how the arrangement and fading of the three primaries yields the complete hue wheel. Its point is a little less obvious than the others, but (I hope) only by a little. If you’ve ever wondered how RGB and the hue part of HSL relate to each other, this visualization should help answer the question.

I think I’m done with visualizing colors for now, but I think I said that before, so you never know. I mean, you know, colors, man! What do they mean?