Missed it the first time through, but here’s a data visualization by The New York Times that demonstrates exactly how devastating a well-designed visualization can be.
I’ve been grappling with a stomach bug the past few days, which was as good a reason as any to unplug from everything I could for a little. Two things I thought were notable as I caught up on my RSS feeds:
Donald Glover Can’t Save You. I lost track of his career after Community–and this article hints that there is a bigger story to tell about that particular series–so this profile was enlightening. I’ll cop to not even having Atlanta on my radar, but this piece convinced me I needed to watch.
I Went To The Olympics and All I Got Was This Tentative Sense of Hope. I have always loved the Olympics–the weirder the sport, the more I want to see it–but the toll they take on the hosting cities and all the corruption pervading the IOC has made that love problematic, to say the least. I liked this article mostly for the small peek it offered into what it’s like to go to an Olympics as a local. As a TV watcher, it was a little — worrying isn’t the right word for it? — that the ads were so repetitive; to me, a sign that Big Corps don’t think Americans watch them, so nobody except big-ticket sponsors are buying. But what do I know about the television industry?
p.s. Just taking a few days away from the news really reinforces the absurd quality that headlines have taken on in the past 402 days. Try it if you haven’t.
Andreas Larsen has solved a problem I’ve been grappling with for a while now but, until I read his work, couldn’t put a name to. In short: CSS gradient fills pop out at you because they have hard edges.
I didn’t know who Sean Vanaman was, either, but he worked on Firewatch. It’s a great, honest conversation about the state of video games that somehow left me, despite so many signs pointing otherwise, feeling that there is still a commercial future for games with strong narrative components.
This post originally appeared on my Patreon.
In other news… that whole Patreon fee thing just turned out to be a lot of needless stress, didn’t it? I’ll post more thoughts on my Patreon in 2018 soon.
Sebastiaan de With’s explanation of how his team redesigned Halide for iPhone X without access to hardware is both impressive and maddening. Impressive because of all the mental gymnastics, maddening because the gymnastics were needed.
His discussion of reachability is spot-on. In this world of bigphones, everything mobile should be designed with this in mind.
This post originally appeared on my Patreon.
I didn’t understand the significance of the email I received from Patreon about fee changes at first. It was written in that shallowly friendly tone that customer-facing tech companies have nearly universally adopted as their style guide, that regardless of its actual content aims to disarm you. It took until I read Jimmy Maher’s explanation that I saw what was afoot. It’s a one-two punch.
First, patrons will pay the transaction fees for their pledges instead of the burden being shared between myself and Patreon. I can see arguments both for and against making this change. Personally, I always looked at the fees as the cost of doing business here. I certainly wasn’t losing sleep over them.
Second, patrons will be charged fees on each individual pledge, not on every credit card charge. These fees no longer have a direct connection to payment processing fees. They’re essentially Patreon turning up the revenue knob.
Patrons who spread their pledges wide-but-thin will feel the pain the most. About 60% of my patrons pledge $1. Already, I have seen one person cancelling their pledge. I wonder how many others will do so once the change goes into effect on the 18th.
I am not sure what I’m going to do. Right now, I am considering my options carefully. I had actually been thinking of adding reward tiers to this Patreon, and had been brainstorming what those could be in the context of open-source development. But now I am not sure where this will end up. I want you to know that I’m thinking about it, however, and I would like to hear your thoughts on the change in the comments. Am I overreacting? Should I think about changing something about my Patreon?
I’ll close with a thank-you to everyone who has supported my work on Twine, whether it’s been with money, an appreciative tweet or comment, or a contribution of code or documentation. What I find most gratifying about Twine is the impact it has had and continues to have. I am so happy that so many of you have made wonderful things with it.
Edit: Natalie Luhrs has posted a deep dive on the numbers involved.