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
Deadlines are bullshit
In software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil.
- External vs. internal deadlines
- Why are internal deadlines evil?
- Engineers who love their work
External vs. internal deadlines
When are deadlines necessary?
- Contractual obligations
- Technical liabilities (e.g., dependency EOL)
- Compliance, government, investors, and other external stakeholders
What do all of these deadlines have in common? They are all important. They are all deadlines that cannot be missed. They are all external.
When are deadlines evil?
- Your manager says you have a deadline
- Your software development methodology says you have deadlines
What do all of these deadlines have in common? None of them are important. They are arbitrary. They are all internal. They are all bullshit.
Why are internal deadlines evil?
- Estimation: When estimating engineering work a substantial time investment is required by an engineer in order to get an accurate estimate.
- Misaligned Incentives: There is an incentive to lie and give estimates much longer than the feature is truly expected to take.
- Low Morale: Deadlines are likely to be missed often. Repeated failure has a cost to the morale of the team.
- Micromanagement: Deadlines are wielded by middle managers as a whip to harass and annoy engineers working on features.
- High Stress: When engineers feel the pressure of other stakeholders holding deadlines over their heads it creates an environment of high stress.
- High Turnover: On teams with high turnover rates the best engineers have an easy time finding new work and leave quickly, the worst engineers have a difficult time finding work and remain. This selects for a lower quality team over time.
Engineers who love their work
The resolution is simple. Never have internal deadlines. Operate on a prioritized and ordered list of features. Estimate only when necessary to prioritize and do so in a t-shirt sizing way. Trust your engineers and they will begin to love their work. Engineers who love their work are happy and productive.