Derek Thompson wrote a wonderful essay on what happens when you become a parent:

The baby you bring home from the hospital is not the baby you rock to sleep at two weeks, and the baby at three months is a complete stranger to both. In a phenomenological sense, parenting a newborn is not at all like parenting “a” singular newborn, but rather like parenting hundreds of babies, each one replacing the previous week’s child, yet retaining her basic facial structure. “Parenthood abruptly catapults us into a permanent relationship with a stranger,” Andrew Solomon wrote in Far From the Tree. Almost. Parenthood catapults us into a permanent relationship with strangers, plural to the extreme.

Paul Ford writes about vibe coding for the NYT (gift link) and what happens when software suddenly becomes cheap and fast to ship:

There are many arguments against vibe coding through A.I. It is an ecological disaster, with data centers consuming billions of gallons of water for cooling each year; it can generate bad, insecure code; it creates cookie-cutter apps instead of real, thoughtful solutions; the real value is in people, not software. All of these are true and valid. But I’ve been around too long. The web wasn’t “real” software until it was. Blogging wasn’t publishing. Big, serious companies weren’t going to migrate to the cloud, and then one day they did.

And then he brings it home in a way that continues to make him one of my favorite web writers:

The simple truth is that I am less valuable than I used to be. It stings to be made obsolete, but it’s fun to code on the train, too. And if this technology keeps improving, then everyone who tells me how hard it is to make a report, place an order, upgrade an app or update a record — they could get the software they deserve, too. That might be a good trade, long term.

We can grieve what we lost, while also being optimistic about the future AI is unlocking for all of us. It’s uncomfortable, but that’s ok, all technological shifts are.

A great list of things to keep in mind when communicating via writing. The article is focused on “managing up” but these principles are relevant in a much broader context as well.

What questions does your manager usually ask? Answer those questions yourself. If you take anything away from this article, make it this. Every manager has their own idiosyncrasies, worldview, values, etc. That’s why the best thing to do is to pattern match. Consider what they’ve asked you in the past, when talking to you or others. Try to give context through that lens.

Source: How I give the right amount of context (in any situation) →

This is a beautifully-written love letter to the CD—and I agree completely:

The commitment for the listener is light—one press of the button—and the challenge for the artist is pleasantly tough. You have to make all the songs work in a row, and there is a very good chance the listener will hear the entire album. One long unbroken work is also like a stage play, which is what I knew best in high school. […] The CD still delights me and helps me frame the idea of a collected set of songs.

Source: Requiem for a Beam →

Wait hold the phone. Frank Chimero is writing again! One of my all-time favorite design writers. Welcome back to my RSS feed, (Internet) friend.

I wanted to get back to walking, reading, and writing. These were the foundational practices during the most prolific and enjoyable parts of my career. I longed to feel generative again and to have ideas with depth, meaning, and pleasant uncertainty, ideas whose remit extended beyond the boundaries of one company. I missed the opportunities of the internet as a common place for finding your people and feeling like a part of a group that actually had ideas instead of opinions or pleas for attention.

Source: Time is On My Side →

This is fun research but did they have to use “reach out” in this quote.

According to a new study, using too much jargon in the workplace can hurt employees’ ability to process messages, leading them to experience negative feelings and making them feel less confident. In turn, they’re less likely to reach out and ask for or share information with their colleagues.

Source: Workplace jargon hurts employee morale, collaboration, study finds →

You know how those of us who read The Lord of the Rings before the movies came out got all weirdly and annoyingly upset about all the “new fans” and how they should have “read the books years ago”? That’s how I feel about the em dash and its AI takeover.

The real issue isn’t me—it’s you. You simply don’t read enough. If you did, you’d know I’ve been here for centuries. I’m in Austen. I’m in Baldwin. I’ve appeared in Pulitzer-winning prose, viral op-eds, and the final paragraphs of breakup emails that needed “a little more punch.” I am wielded by novelists, bloggers, essayists, and that one friend who types exclusively in lowercase but still demands emotional range.

Source: The Em Dash Responds to the AI Allegations →

This is great advice on providing feedback on docs. This especially resonated:

Before starting, remember that the goal of providing feedback on a document is to help the author. Optimizing for anything else, even if it’s a worthy cause, discourages authors from sharing their future writing. If you prioritize something other than helping the author, you are discouraging them from sharing future work.

→ How to provide feedback on documents.

Robin Sloan discusses Substack, and platforms in general, in another excellent post:

Expect enclosure; expect a few big winners; expect advertising, with all the attention-hacking that will demand. Expect, also, that writers will con­tinue to mold their work to fit Sub­stack’s par­tic­ular ecology, rather than “merely” use the tools to pursue their inde­pen­dent visions and ambitions. We learned this about plat­forms a long time ago.

→ Platform reality