Latest / The Feed & The Thread / The Feed & The Thread - September 18, 2026

Transcript

The Feed & The Thread - September 18, 2026 · The Feed & The Thread

• 0:00
  The AI industry is blaming you for its own safety failures.
• 0:03
  That's exactly how the car industry operated in the
• 0:05
  sixties. We're re-living that era, and the design choices
• 0:08
  hiding the risk are now on us.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:17
  Chicago Camps. Leadership By Design is on Thursday and
• 0:19
  Friday, September 17 and 18 and tickets are available now! And
• 0:22
  while you're at it, get caught up on UX fundamentals with five
• 0:25
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:28
  available online at feed and thread dot com to submit your
• 0:31
  feeds, or download our app for all the feeds and threads
• 0:34
  delivered right to your pocket.
• 0:43
  The industry keeps telling us that if it fails, you prompted
• 0:46
  it wrong. That's a dangerous deflection. It shifts the blame
• 0:49
  for systemic flaws onto the user, ignoring the interface's
• 0:53
  actual responsibility. Patrick Neeman at UX Design.cc makes
• 0:56
  this case in "Altman and Amodei’s “unsafe at any prompt”
• 0:59
  moment for AI", drawing a sharp parallel to Ralph Nader's
• 1:02
  critique of the automotive industry. The argument is that
• 1:06
  claiming "prompting" is the user's fault is exactly like
• 1:09
  Detroit blaming drivers for crashes. It ignores the fact
• 1:12
  that automation bias is a documented human flaw, not a
• 1:15
  user error. We need to stop treating bad interface design as
• 1:18
  a user skill gap. Julie Zhuo at The Looking Glass argues in "AI
• 1:22
  for No Good Reason" that AI's real value isn't in automating
• 1:25
  drudgery, but in expanding personal creativity. She
• 1:28
  proposes using AI to build playable board games or
• 1:31
  interactive models, moving beyond productivity metrics. The
• 1:34
  focus shifts to the creative outcome, not the task completed.
• 1:37
  This reframes AI as a tool for leisure, not just labor. Nick
• 1:41
  Babich at UX Planet tests this reality in "I Tested 3 Popular
• 1:44
  Claude Code Skills for Web Design", comparing three popular
• 1:48
  Claude Code skills for web design. He uses a standardized
• 1:51
  prompt for a cleaning service landing page to see where each
• 1:54
  skill breaks down. The results show that even with identical
• 1:57
  constraints, the output quality varies wildly. It proves that
• 2:01
  the tool's default behavior matters more than the user's
• 2:04
  intent. Other articles today from Deque Blog on accessibility
• 2:07
  conference registration and UX Design.cc on designing for
• 2:11
  foldable screens.
• 2:19
  A spring-loaded carousel, a launcher that can't align its
• 2:22
  lock buttons, and a loan application for a master's
• 2:24
  degree. These are the specific, grounded problems filling the
• 2:28
  design feeds today. Over on r/UI_Design, a designer is
• 2:31
  testing a prototype where images stretch with a spring effect
• 2:34
  when the carousel runs out of content. The question is whether
• 2:37
  this tactile feedback feels effective or if it becomes
• 2:40
  disruptive. It's a small interaction, but it highlights a
• 2:43
  bigger issue: when the interface relies on playful physics to
• 2:46
  mask a lack of content, it risks shifting the burden of
• 2:49
  understanding the state onto the user. We need to ask if the
• 2:52
  system is failing to communicate its limits clearly enough. In
• 2:55
  r/UI_Design, someone argues that WhatsApp looks better in light
• 2:58
  mode because the white chat bubbles merge naturally with the
• 3:01
  background. They claim this creates a cleaner visual
• 3:04
  experience than dark mode. This preference for light mode in
• 3:07
  specific contexts suggests that dark mode isn't universally
• 3:10
  superior. It forces us to look past the aesthetic trend and ask
• 3:14
  which visual hierarchy actually serves the user's focus better
• 3:17
  in that specific app. A developer in r/UI_Design is
• 3:20
  struggling with a custom Android launcher, specifically the
• 3:23
  alignment of lock buttons relative to variable-width tabs.
• 3:26
  They're following Material Design guidelines, yet the
• 3:28
  unlocked view lacks cohesion. This is a common trap where
• 3:31
  strict adherence to a design system clashes with the unique
• 3:34
  constraints of a custom component. It reminds us that
• 3:37
  guidelines are a starting point, not a guarantee of visual
• 3:40
  consistency. In r/hci, a frontend developer with a social
• 3:43
  sciences background is asking if a master's in human-computer
• 3:46
  interaction is viable despite a low GPA and high financial risk.
• 3:50
  They're weighing the desire for theoretical depth against the
• 3:53
  practical reality of tuition costs. This tension between
• 3:56
  academic rigor and career ROI is a real barrier for many who want
• 3:59
  to deepen their understanding of user behavior. Finally, over on
• 4:02
  r/UI_Design, a designer is asking how to make a corporate
• 4:05
  app feel family-friendly without looking childish. They're
• 4:08
  looking for advice on typography, color, and
• 4:11
  navigation. This is a difficult balance to strike, but it's
• 4:14
  essential for creating interfaces that feel warm and
• 4:17
  approachable while maintaining a professional standard. These
• 4:20
  discussions show a field constantly negotiating between
• 4:23
  system rules, user preferences, and personal constraints.
• 4:33
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:36
  & Friday, September 17 & 18. It's an online event, so you can
• 4:39
  join from anywhere in the world! Tickets are free, thanks to the
• 4:42
  generosity of the community! If it's within your budget, you can
• 4:45
  purchase a general admission ticket for only twenty six
• 4:48
  dollars - with limited early bird tickets at only fifteen
• 4:51
  dollars. Get tickets now at Chicago Camps dot org.
• 5:00
  Patrick Neeman's piece on AI safety draws a line between
• 5:03
  "prompting errors" and Ralph Nader's critique of the auto
• 5:06
  industry, and that parallel is doing more work than most people
• 5:09
  realize. The industry keeps saying if the AI fails, you
• 5:12
  wrote the prompt wrong. That's a deflection. It shifts the blame
• 5:15
  for a systemic flaw onto the user, ignoring the interface's
• 5:18
  actual responsibility. I hear that, but I think we're missing
• 5:21
  the human element in that equation. Neeman points to
• 5:24
  automation bias as a documented flaw, not a user error. We can't
• 5:27
  just blame the interface if people are wired to trust the
• 5:30
  machine when it looks confident. It's a shared failure, not a
• 5:33
  one-sided one. That's where I push back. If we accept
• 5:35
  automation bias as an excuse, we stop designing for it. Nader
• 5:38
  didn't accept "drivers are careless" as a reason to build
• 5:41
  cars without seatbelts. We built seatbelts. We need to build
• 5:44
  interfaces that catch the bias before it becomes a crash.
• 5:47
  Treating a known human weakness as a user skill gap is a design
• 5:50
  failure, not a human one. Fair enough. But the fix isn't just
• 5:53
  better interfaces. It's a shift in how we value the work. Julie
• 5:56
  Zhuo's argument about using AI for creativity, not just labor,
• 6:00
  is the other half of this. If we keep measuring success by task
• 6:03
  completion, we'll keep optimizing for speed and let the
• 6:05
  judgment calls slide. Right. And that's the disconnect. We're
• 6:09
  building tools that are fast at generating, but slow at
• 6:11
  reasoning. The value isn't in the output anymore. It's in the
• 6:14
  decision to discard it. So the standard has to change. We need
• 6:17
  to measure the quality of the decision, not just the volume of
• 6:21
  the output. That's where the real leverage is.
• 6:25
  That's The Feed and The Thread for today. We'll catch you next
• 6:28
  time!