Latest / The Feed & The Thread / The Feed & The Thread - June 4, 2026

Transcript

The Feed & The Thread - June 4, 2026 · The Feed & The Thread

• 0:00
  Ninety percent of AI content is just crap. That hits hard. We're
• 0:03
  flooding feeds with it. But the real issue is our design systems
• 0:07
  can't handle the noise, so we have to fix the debt first.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:16
  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:26
  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
  We're asking machines to design for us, but we haven't fixed the
• 0:47
  mess we made for ourselves. That tension defines today's Feed.
• 0:50
  Vitaly Friedman at Smashing Magazine argues that AI can't
• 0:53
  fix design debt without explicit human guidance in "How To Make
• 0:57
  Your Design System AI-Ready". The core issue isn't the tool,
• 1:00
  it's the scattered decisions hidden in your codebase. You
• 1:03
  need to treat those choices as infrastructure, documenting
• 1:06
  every spec file so the AI has a strict token layer to follow. If
• 1:10
  you don't audit for hard-coded values now, the AI will just
• 1:13
  invent arbitrary ones later. Chris R Becker applies
• 1:16
  Sturgeon's Law to the current landscape of AI-generated
• 1:19
  content in "AI meets Sturgeon’s Law". He suggests that while AI
• 1:22
  democratized creation, it also flooded the zone with low-
• 1:25
  quality output. More content doesn't mean more value, it
• 1:28
  often dilutes the signal entirely. Designers must build
• 1:31
  stronger filtering mechanisms to cope with this flood of mediocre
• 1:35
  material. Houmahani Kane shares her path from self-taught coder
• 1:38
  to professional creative developer in "Forging Her Own
• 1:41
  Path: Houmahani Kane’s Journey in Creative Development". She
• 1:45
  highlights how specific obstacles in building
• 1:47
  interactive experiences shaped her unique approach. Persistence
• 1:50
  matters here, especially when bridging the gap between
• 1:53
  learning and real client work. Her journey offers practical
• 1:57
  insight for anyone blending code with creative problem-solving.
• 2:00
  Other reads today from CSS- Tricks on offset-path and UX
• 2:03
  Design.cc on the role of the box.
• 2:12
  The community is wrestling with a quiet contradiction today.
• 2:16
  We're asking machines to design for us, yet we haven't fixed the
• 2:19
  messy foundations we built for ourselves. Over on r/UXDesign,
• 2:23
  someone shared a tool called FontPocket that helps designers
• 2:26
  filter and save Google Fonts. It's a small efficiency win, but
• 2:29
  it highlights a larger truth. We're spending energy organizing
• 2:33
  libraries while the core craft of selecting type for clarity
• 2:36
  gets automated. The tool is useful, but it also reveals how
• 2:39
  much of our work is now about managing options rather than
• 2:43
  making choices. In r/UXResearch, a researcher is
• 2:45
  stuck on a survey response that makes no logical sense. The
• 2:49
  participant passed the screener but listed mutually exclusive
• 2:52
  tools. The tension here's between data purity and human
• 2:55
  messiness. Do you discard the outlier to keep the dataset
• 2:58
  clean, or keep it to reflect reality? I think we keep it.
• 3:01
  Real users are inconsistent, and our models need to account for
• 3:05
  that noise, not just the signal. Over on r/UXDesign, a designer
• 3:08
  is asking about swipe gestures in a baby care app. Parents are
• 3:12
  tired, stressed, and often working in the dark. The
• 3:15
  question isn't just about discoverability, it's about
• 3:18
  cognitive load. Popular apps use swipes, but should a critical
• 3:21
  app for exhausted parents rely on a gesture that's easy to
• 3:24
  miss? It's a reminder that familiarity doesn't always equal
• 3:28
  accessibility. In r/UXDesign, the big question is whether AI
• 3:31
  will make designers obsolete in five years. The anxiety is
• 3:34
  palpable, but the answer lies in the difference between output
• 3:38
  and outcome. AI can generate a mockup in seconds, but it can't
• 3:41
  navigate the political nuance of a stakeholder meeting. The value
• 3:45
  isn't in the pixels, it's in the judgment. Over on r/UXResearch,
• 3:48
  someone is choosing between a master's in UX design or
• 3:51
  cognitive science. It's a classic dilemma between
• 3:54
  practical skills and deep theory. My take is simple. You
• 3:57
  need the theory to understand why users behave, and the
• 4:00
  practice to show them how. But right now, the field needs
• 4:03
  people who can bridge that gap, not just pick a side. We're
• 4:07
  building faster interfaces on top of broken processes, and
• 4:10
  that tension is going to define our next career moves.
• 4:20
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:23
  & Friday, September 17 & 18. It's an online event, so you can
• 4:26
  join from anywhere in the world! Tickets are free, thanks to the
• 4:29
  generosity of the community! If it's within your budget, you can
• 4:32
  purchase a general admission ticket for only twenty six
• 4:35
  dollars - with limited early bird tickets at only fifteen
• 4:37
  dollars. Get tickets now at Chicago Camps dot org.
• 4:47
  Vitaly Friedman's point about design debt is structural. If
• 4:50
  you don't audit hard-coded values, the AI just invents
• 4:53
  arbitrary ones. It treats your scattered codebase as a
• 4:56
  suggestion rather than a rule. That's the trap. We're asking
• 4:59
  machines to design for us, but we haven't fixed the mess we
• 5:02
  made for ourselves. The tension isn't the tool. It's the lack of
• 5:05
  a strict token layer to follow. Exactly. And Chris Becker's take
• 5:08
  on Sturgeon's Law connects here. AI democratized creation, sure.
• 5:12
  But it flooded the zone with low-quality output. More content
• 5:15
  doesn't mean more value. It dilutes the signal. So we have
• 5:18
  a flood of mediocre material and no filter. Designers have to
• 5:21
  build stronger filtering mechanisms. But filtering feels
• 5:24
  reactive. We're cleaning up noise instead of defining the
• 5:27
  signal upfront. Maybe the shift is from gatekeeping to
• 5:30
  infrastructure. If your design system can't explain its own
• 5:33
  decisions, it's not a system. It's a wish. The AI exposes that
• 5:36
  fragility. Right. But infrastructure requires
• 5:38
  maintenance. Most teams don't have the budget to treat
• 5:41
  documentation like code. They treat it like a nice-to-have.
• 5:44
  Then documentation becomes the primary deliverable. Not the
• 5:47
  mockup. The spec. That flips the incentive structure. We stop
• 5:50
  valuing the output and start valuing the clarity of the
• 5:53
  input.
• 5:56
  That's The Feed and The Thread for today. We'll catch you next
• 5:59
  time!