Latest / The Feed & The Thread / The Feed & The Thread - April 23, 2026

Transcript

The Feed & The Thread - April 23, 2026 · The Feed & The Thread

• 0:00
  By 2026, designers must ship production-ready code or lose
• 0:03
  their jobs. That sounds like a nightmare for anyone who loves
• 0:06
  visual design. You know it's already 2026, right? And AI is
• 0:09
  the reason we're finally forced to learn how to code. We should
• 0:13
  unpack that.
• 0:18
  Welcome to The Feed and The Thread, brought to you by
• 0:20
  Chicago Camps. There's an open call for speakers for UX Camp
• 0:23
  Summer on May 30th, so now is your chance to get on stage and
• 0:25
  share your ideas! You can use our Proposal Counselor to help
• 0:28
  you get submitted today. The Feed & The Thread is available
• 0:31
  online at feed and thread dot com to submit your feeds, or
• 0:33
  download our app for all the feeds and threads delivered
• 0:36
  right to your pocket.
• 0:44
  When AI reshapes our workflows, we risk solving the wrong user's
• 0:48
  problem or diluting our own expertise. Today's Feed tackles
• 0:51
  that tension head-on. Designing for the elderly reveals a sharp
• 0:55
  conflict between clinical efficiency and human dignity.
• 0:58
  Catherine Chu at UX Design.cc explores this in "How AI may
• 1:01
  reshape elderly care", noting that fear of mistakes often
• 1:05
  blocks older adults from using tech. She argues that true
• 1:08
  consent is nearly impossible when users can't fully grasp
• 1:11
  privacy policies. That forces us to ask who the real user
• 1:14
  actually is. Vague instructions remain the primary reason custom
• 1:18
  AI skills fail in design workflows. Nick Babich at UX
• 1:21
  Planet details this in "7 Common Mistakes To Avoid When Creating
• 1:25
  Claude Skills", showing how missing context leads to generic
• 1:28
  outputs. He insists we must define strict constraints and
• 1:31
  provide robust examples to guide the model. Without these
• 1:35
  guardrails, the tool just becomes a distraction. The 8th
• 1:38
  mistake is not recognizing that skills still get ignored, even
• 1:41
  if you install them. The expectation for designers to
• 1:44
  deliver production-ready code might create a competence trap
• 1:48
  rather than a superpower. Carrie Webster at Smashing Magazine
• 1:51
  makes this case in "The UX Designer’s Nightmare: When
• 1:54
  “Production-Ready” Becomes A Design Deliverable", warning
• 1:58
  that we could become averagely skilled at everything. She
• 2:01
  points to a seventeen percent drop in comprehension when teams
• 2:05
  rely too heavily on generated code. We need to decide if we're
• 2:08
  building systems or just debugging them. Other reads
• 2:11
  today from Intercom on sales agents, iA on data
• 2:14
  visualization, and Codrops on playful animation.
• 2:24
  Welcome back to the daily pulse of our community. Over on
• 2:27
  r/uxwriting, a seasoned professional is wrestling with
• 2:30
  imposter syndrome while watching peers get promoted. The fear
• 2:33
  isn't just about skill gaps, but about the field itself
• 2:36
  shrinking. One commenter bluntly suggested moving laterally to
• 2:39
  product management, warning that content design might disappear
• 2:43
  entirely in five years. This isn't just career anxiety. It's
• 2:46
  a direct signal that when AI reshapes workflows, we risk
• 2:49
  diluting the very expertise that defines our value. In
• 2:52
  r/UXDesign, frustration is mounting over colleagues who
• 2:55
  treat AI as a shortcut to status. People are describing a
• 2:58
  new breed of 'tech bro' obsessed with vibe coding and agent
• 3:01
  automation. One designer shared how painful it's to receive
• 3:05
  feedback that's clearly just a copy-paste from Claude. We're
• 3:08
  seeing teams replace genuine human critique with algorithmic
• 3:11
  responses. When AI makes people insufferable, we aren't just
• 3:14
  losing efficiency. We're losing the messy, essential friction
• 3:18
  that leads to real insight. And we're gaining access to the
• 3:21
  tools that will help bring out the frauds faster than ever,
• 3:24
  folks, so just give it a little bit of oxygen. Over on
• 3:27
  r/UXDesign, another designer is struggling to adjust
• 3:30
  expectations after moving from a fast startup to a massive
• 3:33
  corporation. The shift from three-day turnarounds to slow,
• 3:36
  siloed cycles creates a jarring sense of chaos. This tension
• 3:39
  highlights how our workflows break when scale changes the
• 3:42
  rules. If we can't navigate the difference between speed and
• 3:46
  structure, we risk solving the wrong problem for the wrong
• 3:49
  user. The tension today is clear: AI promises efficiency,
• 3:52
  but it often delivers a hollowed-out process where we
• 3:55
  solve the wrong problems.
• 4:03
  Chicago Camps is hosting UX Camp Summer on Saturday, May 30th.
• 4:06
  There's an open call for speakers so submit your idea
• 4:09
  today! It's an online event, so you can join from anywhere in
• 4:12
  the world! Tickets are free, thanks to the generosity of the
• 4:15
  community! If it's within your budget, you can purchase a
• 4:18
  general admission ticket for only thirteen dollars and fifty
• 4:20
  cents. Get tickets now at Chicago Camps dot org.
• 4:30
  Carrie Webster's piece on the seventeen percent drop in
• 4:33
  comprehension when teams rely on generated code is the real story
• 4:36
  here. That number is terrifying, but I'm seeing it differently.
• 4:39
  The problem isn't the code generation itself, it's that
• 4:42
  we've stopped asking if the output actually solves the
• 4:44
  user's problem. Exactly. When the bar for delivery shifts to
• 4:47
  production-ready artifacts, we trap ourselves in debugging mode
• 4:50
  instead of building systems that serve people. And that connects
• 4:54
  directly to the r/UXDesign thread about the chaos of moving
• 4:56
  from startup speed to corporate structure. We're just swapping
• 5:00
  one kind of blind speed for another kind of hollowed-out
• 5:02
  process. So the risk is that we become efficient at the wrong
• 5:05
  thing. We optimize for the tool's output rather than the
• 5:08
  human outcome, creating a competence trap where everyone
• 5:11
  is averagely skilled at everything. I think that's where
• 5:14
  the real opportunity hides. We need to stop measuring success
• 5:16
  by how much code we can generate and start measuring it by how
• 5:20
  clearly we can define the constraints that prevent the
• 5:22
  model from hallucinating. If the constraint isn't defined,
• 5:25
  the tool is just a distraction. Right. The next generation of
• 5:28
  designers won't be the ones who write the best prompts, but the
• 5:31
  ones who can articulate the boundaries where human judgment
• 5:34
  is non-negotiable. Maybe.
• 5:37
  That's The Feed and The Thread for today. We'll catch you next
• 5:40
  time!