Design: Weekly Summary (December 08-14, 2025)

There’s a quiet hum running through this week’s design conversations. It’s not loud fanfare. It’s more like the sound of someone flicking through a well-thumbed notebook, or the kettle boiling when you’re halfway through a thought. Bits of code, type, color names, candles and maps — they all feel connected, in odd little ways. I would describe them as small course corrections. To me, it feels like people are trying to hold on to the useful parts of the past, while nudging things forward where they can.

Tools and workflows getting closer to people

A few posts this week circle the same idea: tools are changing how designers actually do their work. Luke Wroblewski writes about AI coding agents and how they’re shifting the design-engineering handoff. I’d say his tone is practical, not starry-eyed. The pitch isn’t "AI will replace you," it’s more like "AI will do the boring, brittle bits so you can focus on the part where your head hurts in a good way." Designers fixing production bugs, poking at live code, prototyping faster — sounds almost like having a mechanic who also explains the engine to you while you hold the torch.

Then there’s a more hands-on tutorial vibe from Peter Yang showing how to make branded infographics with Gemini’s Nano Banana. He’s essentially saying: if you give the model a good style guide, it will behave. That’s comforting. It’s also a reminder that tools are only as good as the rules we lay down for them. Like giving a kid a paint set and a color chart — they’ll either paint chaos or follow the chart and make something you can actually put on a fridge.

And a small utility review from Kerrick Long about a hex-color namer ties neatly into those two pieces. Designers love names. Hex codes are precise but cold. A decent naming tool adds a human label to a rigid thing. It’s tiny, but naming is how we remember and argue about color, and arguing about color is fifty percent of the average studio day.

Together these pieces form a pattern: automation and AI are not just flashy toys. They’re getting folded into the daily grind. The conversation is practical, not evangelical.

Process as story: the flipbook, the map, the archive

A thread I liked runs through a couple of posts: the idea that your history matters. You don’t just design for now; you design knowing you’ll look back.

Rob Zolkos made a flipbook video from daily git commits for his app Fizzy. The visual is simple but oddly moving — an 18-month time-lapse of design choices. He writes about making sure the app boots at every commit and about integrating sound. That attention to the archive feels like keeping a family album. It’s fiddly, sometimes boring, but later it’s gold.

Likewise, RJ Andrews and Robert Simmon’s Earth Biomes map shows that iteration matters for different reasons. Maps can be precise or poetic, and they had to balance detail and readability. The post has that cartographer’s patience: you tighten one corner and another loosens. The result is useful to a learner and pleasant to a glance — like a street map that doesn’t make your head spin.

And I’d point you to Artur Piszek on Christopher Alexander’s A Pattern Language. The book is a manifesto for design that grows out of lived life. He talks about light, thresholds, and imperfect finishes — the messy edges that make a house warm. These are reminders that recording how you got somewhere is as useful as the final thing. The flipbook and the map both show that a good design history exposes choices. It’s not vanity. It’s rehearsal notes you can learn from.

The craft vs. trend tension — fonts, UI, and applause

There’s a grumpy vein running through several posts this week. Designers are fed up with fashionable choices that feel hollow.

Nicolas Magand writes about typefaces like they’re outfits. I’d describe his tone as wry. Times New Roman is the old suit that everyone mocks, Helvetica is the uniform some people wear to make meetings go faster, and Verdana is whatever your laptop shipped with. The point is sharp: typefaces carry social signals. They’re not neutral, and overuse or lazy choice drags meaning away. Choosing type isn’t just aesthetics — it’s social choreography.

Nich Heer — yes, that post about UI degradation — takes a similar side-eye to modern polish. He contrasts Windows 95’s blunt, functional honesty with Windows 11’s softer, more ornamental choices. He’s not nostalgic for the pixel; he’s wary of aesthetics that hide friction. It’s like buying a nice jacket with no pockets. Pretty does not always mean useful.

This crops up elsewhere. Jeremy Keith rails against following design trends without asking why. He hates showy gestures that add no value — cookie banners, lengthy intros at conferences, empty flourishes. "Skip intro," he writes, and that hits home: stop doing things because everyone else does them. Be a bit rude and pragmatic.

And that scepticism becomes almost political in The Product Picnic piece. The author argues that UX cheerleading — the ritual praise of process over results — has hollowed out design. When stakeholders treat UX as a ritual to tick off, the actual user benefit can disappear. That’s not an academic fight. That’s an office fight, over coffee and spreadsheets. It’s a fight about whether the boxes you check map to better experiences.

These posts are aligned in mood if not in detail: they push back against fashion without reason. They’re asking for accountability.

Small, thoughtful design: candles, stickers, and the cafe reader

Not everything this week is big-system critique. Some pieces celebrate small touches.

Christopher Jobson shares Gustavo da Mata’s retrofuturistic candles for ÓST. The candles are geometric and quiet. I’d say they feel like a vinyl record in a world of tiny earbuds — an object that invites you to slow down. Candles remind people of hospitality and ritual. When design meets ritual, it often gets dignity.

Robb Knight talks about a sticker shop in his weeknote. There’s a warmth to that. Stickers are low-fi, mobile design. They’re the tiny badges we stick on laptops to declare allegiances: a taste, a joke, a cause. He also mentions a St Jude campaign sticker and a curiosity-run about car-free neighborhoods and transport card designs — small public gestures that shape daily life.

And James' Coffee Blog sketches a concept for a two-panel web reader settings page for Artemis. It’s so sensible it reads like common sense: settings on one side, a live preview on the other. No more guessing what a toggle will do. This is the kind of tidy idea that keeps a user from muttering under their breath. You could implement it in a weekend and feel smug for weeks.

This trio shows a design spectrum. From candles and stickers to pragmatic UI, the attention is to small interactions that matter in daily life.

Data, honesty and the responsibility to make things clear

A few posts drill into the ethics and craft of making information legible.

Saloni Dattani writes a clear, steady guide to data visualization. Her point: charts aren’t ornaments. They reveal patterns you might otherwise miss. She emphasizes clarity, accuracy, and transparency. That bit about responsibility sticks — if a chart is slick but lies by omission, it’s worse than useless. It’s gaslighting, but with pretty colors.

That connects back to RJ Andrews. A world map of biomes isn’t just pretty; it teaches and shapes understanding. The balance between detail and readability matters. You can over-label or under-explain. Either way, someone learns the wrong thing.

There’s a rhythm here: craft + honesty = trust. When designers shortchange either, the output looks like a shopfront that sells pretty boxes and empty promises.

Micro-UI detail: how icons feel and where shadows land

Tiny, focused tutorials have their place too. Nil Coalescing shows how to add an inner shadow to a symbol image in SwiftUI. It’s a micro-lesson, but useful. The effect is subtle — a small depth cue for icons, especially circular ones. These are the flourishes that keep an interface from feeling flat, like adding a little parsley to a dinner plate. They don’t fix structural problems, but they make things feel cared for.

Pair that with the two-panel reader idea and the hex naming tool, and you see a pattern: detail matters. Small affordances, a carefully named color, a shadow that reads as a button — they all add a few points to the total experience.

Awards, platforms and the politics of recognition

Michael J. Tsai has a skeptical take on Apple’s 2025 App Store Awards. He questions choices and the overall direction of Apple’s design sensibility. The example of Tiimo, an app for people with ADHD that lacks a Mac version, pokes at a wider problem: recognition isn’t neutral. Choosing winners says something about values.

This ties back to the critique of cheerleading. Awards and lists shape what people copy. If the awards skew toward shiny, consumable things, others follow. It’s like cooking shows: the more you applaud plated tricks, the more restaurants try to imitate them, even if they make less sense for real diners.

Voice, metaphor, and a few human images

A bunch of the posts use simple metaphors to make a point. Typefaces as clothes, maps as quilts, flipbooks as photo albums. I’d describe these metaphors as helpful. They don’t over-explain. They give you a quick mental picture.

There’s also a recurring local flavour. Talk of Aston Martin Cygnet in a weeknote feels very British — a little wink to car fetish culture. A mention of car-free neighborhoods reads like a European magazine clipping. Little regional touches make the conversation feel lived-in. It’s not an academic paper. It’s people nodding across coffee cups.

The mood flips between admiration and impatience. People admire craft and clarity. They’re impatient with hollow gestures, and they’re impatient with a certain kind of design celebrity that confuses trend for substance.

Where people agree and where they don’t

Agreement is mostly around two points. First: details matter. That shows up in the flipbook care, the inner shadow tutorial, the hex namer, and the reader preview idea. Second: accountability matters. That shows up in the posts about UI degradation, UX cheerleading, and the "skip intro" call.

Disagreements are smaller and more interesting. Some posts celebrate tools as extensions of practice (Luke Wroblewski, Peter Yang), while others warn that trends and awards nudge behavior in the wrong direction (Jeremy Keith, Michael J. Tsai). Those views aren’t mutually exclusive. One can love tools and still scold the culture that idolizes surface over function.

Design as ethics and lived life

A throughline that surprised me is the repeated ethical angle. Not ethics in the abstract, but the mundane kind: how charts can mislead, how awards define taste, how UX rituals can displace real value. The writing isn’t preachy. It’s more like a neighbour tapping their watch and saying, gently, "don’t forget why you’re doing this."

There’s also the lived-life angle. Artur Piszek and Christopher Alexander remind us that buildings are for living. RJ Andrews and Rob Zolkos remind us history matters. These aren’t flashy topics, but they underlie everything else. If you build a nice app but it makes people feel lost, you’ve missed the point. If your map looks pretty but teaches the wrong pattern, you’ve done harm.

Little pleasures and the occasional rant

Some pieces are just nice to read. The candle post is like a little stop in a gallery. The sticker shop note is a wink. The flipbook is quietly satisfying — like watching timelapse gardens grow.

Then there are the rants. The Windows UI piece and the UX cheerleading post have that delicious impatient energy. They remind you that not everyone has to be polite in the same way. Sometimes a loud complaint helps more than a polite suggestion.

If you want to chase threads further

There’s lots to read if you want to follow the breadcrumbs. The flipbook is one of those posts you want to watch and then re-watch. The data viz guide hides useful rules you might keep on a sticky note. The two-panel reader concept looks like something you could try in a side project. The Typefaces-as-clothes piece has playful examples you might actually use to explain typography to someone who thinks fonts are a trivial choice.

A few questions keep circling back. How do we make tools that push craft without pushing fads? How do we teach readers to expect clarity in charts, not just beauty? How do we keep design accountable when it’s easier to applaud than to critique? None of the posts pretend to have final answers. They offer a set of nudges.

If you like tidy how-to tips, check the SwiftUI shadow trick and the Nano Banana walkthrough. If you like slow craft, read the Fizzy flipbook and the map-making story. If you like a straight-talking critique, the pieces on UI degradation and UX cheerleading have bite.

I’d describe the week as pragmatic and mildly cross — not angry, but fussy in a good way. It feels like people are saying: mind the details, name things, keep the history, and don’t let applause replace judgment.

There’s a certain comfort in that. It’s like swapping recipes with a neighbour. You’ll get a tip or two, and also an eye-roll about modern flourishes. Read the posts. Some of them will teach you a trick. Others will make you think twice about the tricks you were about to copy.