culture
Cupcakes and froyo
A squeezable nugget of comfort
I was waiting for the perfect image to start blogging the idea, and last week supplied one: the Celestial Buddies plush toy that rode on the Crew Dragon test flight. The symbolism is perfect: an oddly satisfying little squeezable nugget of comfort within the disorienting, weird domesticity of a spaceship.
Domestic cozy is in an attitude, emerging socioeconomic posture, and aesthetic, that is in many ways the antithesis of premium mediocrity. Unsurprisingly, it takes its cues from the marginal shadow behaviors of premium mediocrity.
The Big Lie
“We only give them what they want.”
This is The Big Lie of mass culture and of debased art, and also it is the weak excuse for the cultural default of many designers.
Millennials and Gen. Z
I made a prediction on Twitter on February 6th: If Millennials (b. 1980 – 2000) were the premium mediocre generation, Gen Z (b. 2000 – 2020) is going to be the domestic cozy generation.
Cultural relevance
More than ever, people are choosing how to spend their time based on the amount of attention they can garner—and you and I are no exception. Everyone is susceptible to this logic. But what I want to argue in this piece is that tech startup founders are particularly susceptible to this tendency.
Working at and around startups for several years, I’ve noticed many founders prioritizing culture, visibility, and perception over product, customer development, and strategy. Maybe this is to be expected in a time where culture moves faster and is perceived as more important than ever. But I find it unusual that the tech industry seems unaware of a whole class of typical mistakes founders make in pursuit of cultural relevance.
Avant-Garde and Kitsch
An Essay by Clement GreenbergCapitalism in decline finds that whatever of quality it is still capable of producing becomes almost invariably a threat to its own existence.
The Third Way
An Article by Kevin KellyBut all the civilized cities of the world were also filled with third places that people loved. Not quite private, not quite public, these third places were intimate but open to anyone. Like settling down at a table at a cafe. It felt like your space, but you were not the landlord. They were public, open spaces that you could “own” for a while.
…We need a new third category of work — something between “employee” and “not an employee”—that encompasses digital gig laborers. AirBnB is neither a hotel, nor a private resident. It is a third thing, and we need to create a new category to deal with it…This is the era of the third way.
You Don't Need To Do The Farmhouse Home Aesthetic When You Decorate
An Article by Kate WagnerIt took two decades for HGTV and its ilk to streamline the process of creating design hegemony — to perfect the concept of having multiple shows congeal around the same aesthetic rather than let them exist at the whims of their individual hosts, as was more the case in the 2000s. While previous eras of design (think midcentury modernism) were spearheaded by architects, interior designers, and other tastemakers, in the late ’90s, capital-A Architecture lost interest in the home — deconstructivist ideas and new, high-tech forms were better suited to museums and universities — and a coalition of real estate developers, home improvement and furniture stores, and TV decorators stepped in to take their place. The worlds of high culture and popular consumption in residential design have never been more separate, and, in this critic’s opinion, both suffer as a result.
Class 1 / Class 2 Problems
An Article by Kevin KellyThere are two classes of problems caused by new technology. Class 1 problems are due to it not working perfectly. Class 2 problems are due to it working perfectly.
...Class 1 problems arise early and they are easy to imagine. Usually market forces will solve them. You could say, most Class 1 problems are solved along the way as they rush to become Class 2 problems. Class 2 problems are much harder to solve because they require more than just the invisible hand of the market to overcome them.
...Class 1 problems are caused by technology that is not perfect, and are solved by the marketplace. Class 2 problems are caused by technology that is perfect, and must be solved by extra-market forces such as cultural norms, regulation, and social imagination.
Monoskop
A WebsiteMonoskop is a wiki for the arts, media and humanities.
Scenius
Scenius stands for the intelligence and the intuition of a whole cultural scene. It is the communal form of the concept of the genius.
Premium Mediocre
An Article from Ribbonfarm by Venkatesh Rao
Beyond Artboards
The Pursuit of Lossless Design-Development Handoffs.
Can't developers just see?
We designers love artboards. From rough UI sketches to high fidelity mockups, we see ourselves as visual artists expressing ideas on artboards that have a pre-defined width and height. To start a new project, we declare the size of the artboard in the first step.
What about responsive design? Not a problem! We diligently design on three artboards — one for mobile, one for tablet, and one for desktop — with content elegantly adapting, scaling, reflowing, reordering, and reprioritizing. We proudly hand off the artboards to developers while patting ourselves on the back: this is how responsive design should be done.
After weeks of arduous engineering, the product finally comes out. We find, to our great dismay, that some copy is hanging off the grid, the focal point of the hero image has been cropped out, the font sizes don’t even come close to the type ramp. What went wrong? Can’t the developers just see everything on all those artboards?
Nope.
We are the ones who paved the path
No matter how many screen sizes our artboards account for, some user’s browser will break loose from our prescription. With users resizing, rotating, and zooming the screen, new devices stretching, squashing, curving, and cutting (e.g. the speaker area in iPhone X) the screen, the sizes become infinite. Good luck making an artboard for each one of them.
Artboards are a lossy format. Using artboards in a handoff is a lossy process. When we pitch a finite number of plans against an infinite number of situations. We inevitably get in-betweens. Once there are in-betweens, there are unknowns. Once there are unknowns there is guesswork. Once there is guesswork, there are surprises. Engineers take the path of least resistance. We are ones who paved the path.
Until we get there
- As a designer, learn writing HTML, or better still, semantic HTML. If coding up the entire design is too hard, try coding up one component at a time, and not worrying about CSS. The HTML alone will prove invaluable for developers to understand the content structure. In addition, you are forced to optimize the information architecture as you work out the code from content.
- If coding by yourself is out of the question, pair up with the engineer who will receive the design. Work closely with him or her to prototype the design, validate responsive behaviors, and obtain feedback on the feasibility. Don’t call it an iteration until the design has seen played with in code.
- As a manager for large enterprise, co-locate your designers and developers, encourage interdisciplinary learning, understand that each minute spent on coding before the handoff translates to ten minutes saved from changing and fixing issues after the handoff.
- As a stakeholder in the handoff meeting, give the designer a thumbs-up when he or she demos live code running in browsers in place of mockups on artboards. That’s a design champion you are looking at.