Latest / The Feed & The Thread / The Feed & The Thread - October 19, 2026

Transcript

The Feed & The Thread - October 19, 2026 · The Feed & The Thread

• 0:00
  Designers are treating code as their primary material, not just
• 0:03
  static images. Wait, so we're building like architects?
• 0:06
  Exactly, and that's where the real craft lives in the shipped
• 0:09
  product.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  Chicago Camps. The Feed & The Thread is available online at
• 0:19
  feed and thread dot com to submit your feeds, or download
• 0:21
  our app for all the feeds and threads delivered right to your
• 0:24
  pocket.
• 0:32
  The boundary between designing and building is dissolving, and
• 0:35
  with it, the assumption that our job ends at handoff. Nil
• 0:38
  Thyrion at UX Design.cc lays out this shift in "Beyond the
• 0:41
  Canvas", arguing that as code generation becomes easier,
• 0:44
  design is becoming the primary differentiator. This is about
• 0:48
  ownership. New Figma capabilities allow AI agents to
• 0:50
  act as genuine collaborators with shared context, moving
• 0:53
  beyond transactional prompt-and- response interactions. The role
• 0:57
  of the design engineer is expanding to include
• 0:59
  accountability for the actual user experience. Jeff Gothelf
• 1:03
  at his own blog challenges the idea that project management has
• 1:06
  vanished in "How to determine how much project management work
• 1:09
  a product manager should handle". Instead, the work has
• 1:12
  migrated. Product managers are now the default owners of dates,
• 1:16
  dependencies, and status updates, often alongside design.
• 1:19
  This analysis reveals that while dedicated Project Managers may
• 1:22
  be absent from core product teams, the coordination work
• 1:25
  remains, just redistributed. The uncomfortable truth is that
• 1:28
  product managers are absorbing a burden they were never
• 1:31
  explicitly hired to handle. Jon Sabutis at UX Design.cc argues
• 1:35
  in "Design in the material you ship" that digital designers
• 1:38
  should treat code as their primary material, similar to how
• 1:41
  an architect understands stone. He cites Ayn Rand to illustrate
• 1:45
  that purpose, site, and material determine shape, suggesting
• 1:48
  responsive layouts belong to the browser. Design files often fail
• 1:51
  to capture real-world states like loading errors or keyboard
• 1:54
  navigation, leading to drift between design and
• 1:57
  implementation. If we don't engage with the code, we're
• 2:00
  designing a ghost, not a product. Other reads today from
• 2:03
  UX Design.cc on AI setting us free and designing personalities
• 2:06
  rather than interfaces.
• 2:15
  Today's discussions circle a single friction point: the gap
• 2:18
  between what we design, what we build, and what the user
• 2:21
  actually feels. Over on r/hci, a practitioner is arguing
• 2:24
  that the Slow Technology framework lives or dies in its
• 2:27
  details. They point to the slow doorbell as the perfect example
• 2:30
  of reflective slowness, which is a chosen engagement, rather than
• 2:34
  annoying slowness, which is just bad design. This distinction
• 2:37
  matters because it shifts the goal from eliminating delay to
• 2:40
  curating attention, and that's a different kind of design work
• 2:43
  entirely. In r/UI_Design, a junior designer is asking how to
• 2:46
  replace generic, AI-looking buttons with something that
• 2:49
  feels intentional. The frustration here's real, as the
• 2:52
  homogenized aesthetic of auto- generated interfaces is becoming
• 2:55
  a default that designers are now having to actively fight
• 2:58
  against. It's a sign that visual consistency is no longer just
• 3:02
  about brand guidelines, but about asserting human agency in
• 3:05
  the craft. Over on r/DesignSystems, a senior AEM
• 3:07
  practitioner is pointing out that Figma components often fail
• 3:11
  to reflect what content authors can actually configure in
• 3:14
  production. They propose a component contract that
• 3:16
  documents real constraints and approved variants, flagging any
• 3:19
  discrepancies between the design file and the live system. This
• 3:23
  is a direct challenge to the handoff model, suggesting that
• 3:26
  design tools must speak the same language as the CMS to avoid
• 3:29
  wasted effort. In r/UI_Design, a developer is
• 3:32
  experimenting with replacing static loading text with a
• 3:34
  dynamic light effect around the chat input. They're trying to
• 3:38
  make the wait for local AI models feel less like a dead
• 3:41
  zone and more like a process in motion. It's a small
• 3:43
  interaction, but it highlights how we're starting to design for
• 3:47
  the patience of the user, not just the speed of the machine.
• 3:50
  Today's threads all point to the same place: the work doesn't end
• 3:53
  when the file is exported, it continues in the details of how
• 3:56
  the system behaves, how it feels, and how it respects the
• 3:59
  user's time.
• 4:07
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:10
  For a weekly and monthly exploration of the patterns and
• 4:13
  signals across UX, you can also check out Patterns and Signals
• 4:16
  at the website patterns and signals dot com. Chicago Camps
• 4:19
  will have more events in 2027. You can submit to be a speaker
• 4:22
  at a future event at Chicago Camps dot org.
• 4:31
  There's a specific line in Jon Sabutis' piece that really stuck
• 4:34
  with me, where he says that if we don't engage with the code,
• 4:37
  we're designing a ghost. And that's not just a metaphor. It's
• 4:40
  a diagnosis of why the gap between our Figma files and the
• 4:43
  live product feels so wide right now. I hear that, and I get the
• 4:46
  frustration. But I'd push back on the idea that this is just
• 4:49
  about designers learning to code. The friction I see in the
• 4:51
  community is that our components are lying. We have a senior
• 4:54
  practitioner on r/DesignSystems pointing out that Figma
• 4:57
  components often don't reflect what content authors can
• 4:59
  actually configure in production. We're designing for
• 5:02
  a static state that doesn't exist in the dynamic reality of
• 5:05
  the CMS. That's a critical distinction. Sabutis argues that
• 5:07
  design files fail to capture real-world states like loading
• 5:10
  errors or keyboard navigation. So when we say we're designing a
• 5:13
  ghost, it's because we're ignoring the behavior. The
• 5:16
  material is the logic that determines whether a button is
• 5:18
  enabled or disabled based on user data. If you don't
• 5:21
  understand that logic, you're not designing the product.
• 5:23
  You're just decorating a placeholder. And that's where
• 5:26
  the AI angle gets tricky. We see juniors on r/UI_Design
• 5:29
  struggling to make buttons feel intentional, fighting against
• 5:31
  that homogenized aesthetic. But if the underlying component
• 5:34
  contract doesn't define the constraints, no amount of visual
• 5:37
  tweaking fixes the drift. We need to stop treating the
• 5:40
  handoff as the finish line. The work continues in how the system
• 5:43
  behaves. Exactly. The boundary is dissolving, and with it, the
• 5:46
  assumption that our job ends at export. Sabutis cites Ayn Rand
• 5:48
  to say purpose, site, and material determine shape. So if
• 5:51
  the material is code, then the shape of the interface has to be
• 5:54
  derived from the capabilities of the code. Not the other way
• 5:57
  around. I like that reframing. It moves the discussion from
• 6:00
  "designers should learn JavaScript" to "designers need
• 6:02
  to understand the constraints of the system they're building in."
• 6:05
  It's about literacy. And that's a skill we can actually build.
• 6:08
  So the takeaway is that the definition of "ready for
• 6:11
  development" has to change. We can't hand off a static image
• 6:13
  and call it done. Right. The standard for a finished design
• 6:16
  has to include the behavior. If it doesn't account for the
• 6:19
  loading state, the error state, and the real-world data, it's
• 6:22
  incomplete. That's the new baseline.
• 6:26
  That's The Feed and The Thread for today. We'll catch you next
• 6:29
  time!