Design: Weekly Summary (September 29 - October 05, 2025)

I would describe this week's batch of design writing as a kind of rummage through a very particular shed. There are big, stubborn tools — like the idea of design as something you can teach to folks who don't want to be designers — and there are small, shiny things — a notes app here, a wallet there. To me, it feels like a week where people kept returning to two things: how design turns into habit or language, and how tools shape what we think of as good design. I’d say there's a clear tug-of-war between making things simple for everyone and keeping the craft alive.

Teaching design to people who don't want to be designers

Will King wrote a short, stubborn note called "Course Memo: An Impossible Problem." He frames a problem that looks obvious but is oddly hard. How do you teach design fundamentals to people who may never want to be practicing designers? He wants the course to matter for every student, not just the future designers in the room. He wants theory that doesn’t feel like abstract homework and exercises that aren’t just busywork.

Reading it, I’d say his struggle feels like trying to teach someone to make a decent cup of tea when they only ever drink coffee. You can show the kettle, the leaves, and the stirring. You can make it tasty. But if they never intend to steep anything again, you must make the lesson useful in a different way. That’s the problem he’s chasing. He keeps circling the compromise between theory and practice. Too much theory and students check out. Too much practice and they miss the thinking behind the choices.

He admits it’s hard. He calls it rewarding. That’s about as honest as you get. The post makes you think the right course would be small, rough, and practical. It should hand people tools they can actually use. Not a syllabus of elevated terms. Not a parade of case studies that only designers enjoy. The sketch here is promising. It reads like someone trying to make a recipe that a whole family can eat — and keep everyone at the table.

Little things, big love: tools and taste

Then there’s the thing about tiny pleasures in design. Cartoon Gravity put together "Wednesday Wonders 9," a nice scatter of tools and creators that all feed into how folks make things and feel about making them. Craft, the notes app, gets a lot of affection. It’s praised not just for being pretty, but for being part of a "LifeOS" — which, to me, is a fashionable way of saying “a system that helps you live and get work done.” The writing treats Craft like a neat butter knife: not flashy, but it spreads well.

There’s also a nod to Austin Kleon. His old chestnuts like Steal Like An Artist crop up because people keep needing that reminder: creativity is remixing with care. Then there’s music — Sven Wunder’s album "Daybreak" gets a shout. That part feels like a breath of fresh air. Music, the post hints, shapes how design feels. It’s not just about pixels. Qobuz — a music service — is praised for high-quality audio and better artist payouts. Here’s a tiny social stance in a tool review. And finally, Secrid, a wallet brand, is admired for making something small and clever.

To me, this post is like someone showing you a neat set of kitchen gadgets. Not everything is for everyone, but each thing has a use. It quietly suggests that design isn’t only what you make on a screen. It’s the texture of your playlist, the weight of your wallet, the way your notes app nudges you to do the next thing.

Interfaces as languages, not ornaments

Ben Follington wrote "Interfaces are languages," and it’s the kind of essay that sits in your head and refuses to leave politely. The main idea is sharp: interfaces aren’t just visual shells slapped on software. They are languages. That is, they carry grammar, idioms, conventions, and a way for people to become fluent.

He’s not thrilled with the current rush to let large language models (LLMs) become the main interface to software. I’d say he casts LLMs as a kind of charming translator who never actually teaches you the dialect. LLMs give flexibility and answers, sure. But they can stop users from developing a shared meaning with the system. You get quick results but no fluency. The software remains a one-off conversation instead of a place you speak comfortably, day after day.

Ben pushes for designing digital languages that evolve. He wants small, safe changes that let meaning grow through use. There’s a bit of a cautionary note. If you lean on LLMs too soon, tools become more brittle in the long term, because the shared language never forms. To me that’s a useful image. It’s like learning to drive a car where the GPS tells you everything but you never learn the back roads. You might get places fast, but you never form a map in your head.

The essay doesn’t dismiss LLMs. Instead, it asks designers to hold them to account. Use them, yes, but not as a replacement for the slow work of building shared conventions and fluency. I’d say that is a tidy tension in this week’s writing: speed and flexibility versus practice and craft.

Drawing tools and the trade-off of convenience vs control

Michael Drogalis walked through his drawing and diagramming toolchain. This is the kind of post where you nod and think, yes, that’s what I do too — but then you notice a slightly different choice and your head tilts. Michael likes four tools: Excalidraw, Figma, Omnigraffle, and MacOS Preview.

Excalidraw, the freehand sketch app, is loved for being immediate. It’s like grabbing a napkin and drawing. Figma is praised for pixel control but gets dinged for not being a great diagramming tool. Omnigraffle is the middle path — a bit of both. And Preview? It’s the plain screwdriver in the drawer. It opens PDFs and does the small edits you need when nothing else is handy.

I would describe this set as practical and honest. The post is a reminder that every design workflow is a little ragtag. Some days you want the flourished, controlled tool. Some days you want the sticky notes and the sharpie. He suggests using the right tool at the right time. You don’t try to fillet a fish with a spoon. You don't try to make a precise interface with just a freehand sketch. But you also don’t need a full toolset for every small idea.

The piece quietly hints at a deeper point: tool design matters because it shapes thought. If your diagram tool encourages formal boxes, you’ll think in boxes. If your sketching tool encourages rough lines, your ideas stay playful. That circles back to Ben’s language idea. Tools give people a grammar.

Audio, interviews, and stories that shape design choices

There were a couple of audio-related posts this week. GreyCoder offered a neat curated list: 150 podcasts worth listening to. A long list like that is like finding a box of old records in a market stall. There’s history, philosophy, design, and storytelling. It’s generous. The list names things you probably know — like Michael Lewis’s "Ideas Against the Rules" and Seth Godin’s "Akimbo" — but also points to lesser-known gems. I’d say it’s a map for anyone who wants to let other people’s voices shape their practice.

Matt Mullenweg wrote something called "Telegram and Weird Al," which at first glance sounds odd. Inside, he talks about an interview with Pavel Durov, the founder of Telegram, by Lex Fridman. There’s admiration for Durov’s engineering philosophy and the odd ways product decisions get made. Matt also points to a lighter chat between John Mayer and Weird Al Yankovic. They’re not design people, but their ways of working — the choices, the habits, the craft — are instructive.

To me, this cluster of audio pieces is a reminder that design isn’t isolated. Decisions in architecture, platforms, music, or jokes all have design fingerprints. The Telegram interview touches on things like resilience, privacy, and speed. These are design choices as much as they are engineering ones. And the Mayer/Weird Al conversation speaks to playfulness and craft. Both are useful for designers who want more than wireframes: they want temperament.

The music and audio notes from Cartoon Gravity tie here too. The post’s praise of Qobuz and Sven Wunder suggests that how things sound matters. Design isn’t only sight. Audio affects mood and rhythm. It changes how people use tools.

Patterns, agreements, and a little disagreement

Read across these posts and a few patterns stand out.

• Design as a language: Ben’s essay is explicit about this. Michael’s toolchain post implies it. Will’s course memo wants students to learn the grammar so they can speak it. People are returning to the idea that design isn’t decoration. It’s a learned system.

• Tools shape thought: That was a tiny anthem this week. Whether it’s Craft nudging someone’s LifeOS, Excalidraw making sketches fast, or Qobuz nudging musical taste, the message is clear. Use different tools and you get different habits.

• A tension between accessibility and craft: Will King’s memo captures the hardest bit. Make design useful for non-designers but not dumbed down. Ben worries that LLMs make things too ephemeral. Michael’s tool choices show ways to keep both speed and control. The disagreement is less about values and more about time horizon. Some writers are thinking about now. Some are thinking about how fluency forms over months and years.

• Small physical details still matter: Secrid’s wallet, Qobuz’s audio quality, the feel of a notes app. These are reminders that physical and sensory things still influence how we think about digital design. It’s not all pixels and prompts.

There aren’t sharp fights. Mostly there are nudges in similar directions. People seem to agree that design needs both generosity and rigor. They differ when it comes to method. Be pragmatic, some say. Build slow grammars, say others. Try new tools, others say. The chorus is friendly but not chorus-like; it’s an ensemble where each instrument is playing its own tune.

Tangents worth chasing

A few small digressions in these posts are worth a look. Will’s memo slides into practical pedagogy — not a full lesson plan, but hints about exercises. That’s the kind of thing you can steal and tweak. Ben’s language idea makes me want to read his other essays about safety and evolution in software. Michael’s tool notes include little tricks and keyboard habits that feel like insider chatter. Cartoon Gravity’s list of wonders includes one or two recommendations that seem oddly personal. GreyCoder’s podcast list has hidden gems you’ll only find by scanning it.

One odd little tangent: the political economy of music platforms. It appears in Cartoon Gravity’s praise of Qobuz and in Matt Mullenweg’s reflexes about how platforms run. It’s not the main story, but it bubbles up. Artist compensation and the quality of delivery shape what people make. That in turn shapes what designers need to design for. If artists are paid fairly, the music they make will be different, and those differences affect UI choices. It’s a small loop, but it’s there.

Things you might try this week

If you want a couple of practical takeaways that jump straight from these posts, here are a few ideas I found myself repeating while reading them.

• Try Excalidraw for quick thinking. Use it to sketch problems before you open Figma. It’s fast. It lowers the bar to get something down.

• Think about interfaces as languages. When you design a flow, ask: what grammar does this teach the user? Is it consistent? Can it grow?

• If you teach non-designers, give them bite-sized, practical tasks. Not one big theory lecture. Make it a sandwich. Show them one interesting choice and let them taste it.

• Check out a podcast or two from GreyCoder’s list. Listening to other people’s ways of thinking is like letting new spices into the kitchen.

• Try Qobuz or anything that improves your listening quality for a week. Pay attention to how different music changes the way you make things.

• Don’t underestimate the small physical objects. A good wallet, a tidy notebook, a notes app with the right friction — they add up.

Where the conversation might go next

There are obvious next questions from these posts. What happens if we accept Ben’s thesis and actually treat interfaces as growing languages? How do we design curricula that let people become fluent in a few essential design idioms without turning them into professional designers? How should tools change if we accept that they shape thought? And what responsibility do platforms have to creators, when audio and music affect the whole culture of design?

I’d say the week gestures at three possible moves. One: make tooling that respects both speed and fluency. Two: build teaching experiments that measure usefulness, not just test scores. Three: keep listening — to podcasts, to music, to conversations with people who aren’t designers — because design borrows from everywhere.

If you want the full arguments, the fuller examples, and the soft edges, go read the posts. Will’s quick memo is a good place if you’re thinking about curricula. Ben’s piece is the one to return to when you’re worried about LLMs taking shortcuts. Michael’s toolchain is the kind of list you’ll keep open in your tabs. Cartoon Gravity hands you a short list of beautiful things. GreyCoder gives you an index of voices you can follow. Matt’s note ties a few conversations together and reminds us that personality and engineering both shape the product.

It feels a bit like being in a small town market. You stop at a farmer’s stall and buy onions. Then you wander into a music shop for a record. You pick up a pamphlet about learning to cook. Different stalls, same market. Different posts, same conversation. They don’t fully agree. They don’t have to. But together they make a useful day. If any of these paths pull you, the longer pieces are waiting with more detail and argument. Dig in, and see which tools and ideas become part of your own grammar.