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

Transcript

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

• 0:00
  AI is exposing a craft crisis in design. So we're losing the
• 0:03
  basics? It's not just skills, it's that users don't actually
• 0:07
  see your design system.
• 0:12
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. Leadership By Design is on Thursday and
• 0:17
  Friday, September 17 and 18 and tickets are available now! And
• 0:20
  while you're at it, get caught up on UX fundamentals with five
• 0:23
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:26
  available online at feed and thread dot com to submit your
• 0:29
  feeds, or download our app for all the feeds and threads
• 0:31
  delivered right to your pocket.
• 0:40
  We keep building systems that look organized to us but feel
• 0:43
  fragmented to users, while the tools meant to help us are
• 0:46
  exposing gaps in our foundational craft. Clément
• 0:49
  Grellier at Codrops details this in "Building an Infinite Loom:
• 0:53
  Unravelling Images into Threads with Three.js", showing how he
• 0:56
  breaks images into twenty-six independent ribbons rather than
• 0:59
  one stretched plane. This avoids vertex artifacts and lets each
• 1:03
  strip drift at its own speed based on screen proximity. The
• 1:06
  result is a weave that frays naturally at the edges, turning
• 1:09
  a standard slider into a tactile unraveling experience. It proves
• 1:13
  that geometry matters more than resolution when you want motion
• 1:16
  to feel physical. Fabricio Teixeira at UX Design.cc
• 1:19
  highlights the craft crisis in "Blank pages, Researcher-in-the-
• 1:22
  loop, Design’s craft crisis", where AI exposes shallow skills
• 1:26
  and pushes for a Researcher-in- the-loop model. We need humans
• 1:29
  to govern AI research to keep ethics visible, not just chase
• 1:32
  quantitative futurism that misses user nuance. The
• 1:35
  legibility gap widens when small samples get dismissed, hiding
• 1:38
  the real journey behind clean data. We risk losing the human
• 1:41
  context if we trust the model more than the method. Chris R
• 1:45
  Becker at UX Design.cc applies Gestalt psychology in "Users
• 1:48
  don’t see your design system", reminding us that users see
• 1:51
  wholes, not component lists. The Law of Simplicity means our
• 1:54
  brains naturally organize stimuli into their simplest
• 1:57
  form, regardless of our design system's complexity. If we
• 2:00
  ignore this, our structural intent fails because perception
• 2:03
  doesn't care about our documentation. We must design
• 2:06
  for the pattern the eye creates, not the hierarchy we built.
• 2:09
  Other reads today from Codrops on ASCII rendering, UX Design.cc
• 2:13
  on color scheming, and Rosenfeld Media on conference tickets.
• 2:23
  Designers are navigating a strange gap between how systems
• 2:26
  look to us and how they actually feel to users, while the tools
• 2:30
  we rely on expose cracks in our foundational craft. Over on
• 2:33
  r/hci, a student with a dual major in computer science and
• 2:36
  cognitive science is asking how to build a resume that bridges
• 2:39
  technical skill with human understanding. The question
• 2:42
  reveals that the field still struggles to define what HCI
• 2:45
  actually is, sitting as it does between engineering and
• 2:47
  psychology. It matters because we need practitioners who can
• 2:50
  speak both languages, not just one, if we want to build systems
• 2:54
  that are organized for the business but intuitive for the
• 2:57
  person using them. In r/UserExperience, a designer is
• 2:59
  wrestling with a date range picker, specifically how to
• 3:02
  handle invalid states for the second field. The tension is
• 3:05
  between highlighting a specific error with a red icon versus
• 3:08
  disabling fields to prevent mistakes altogether. This isn't
• 3:11
  just about pixels, it's about whether we trust users to
• 3:14
  correct their own inputs or if we should design out the
• 3:17
  possibility of error. It highlights a gap in our craft
• 3:20
  where we often prioritize visual clarity over actual usability,
• 3:23
  leaving users confused by systems that look clean but feel
• 3:26
  rigid. Over on r/UXResearch, a recent experimental psychology
• 3:29
  PhD graduate shares the difficulty of entering the field
• 3:32
  after facing rejection from major tech companies. The
• 3:35
  disconnect is stark, with hiring managers prioritizing specific
• 3:38
  programming knowledge like R over the rigorous methodological
• 3:41
  training the candidate already possesses. It underscores a real
• 3:44
  problem where the tools meant to help us hire are actually
• 3:47
  filtering out deep foundational expertise in favor of
• 3:50
  superficial technical checks. We risk building a profession that
• 3:53
  looks organized on paper but lacks the theoretical depth
• 3:56
  needed to solve complex human problems. In r/hci, researchers
• 3:59
  are exploring how measuring cognitive effort during
• 4:02
  interaction can serve as proof of human identity, raising
• 4:05
  questions about user comfort and confidence. The idea of real-
• 4:08
  time attestation of work touches on the uneasy feeling of being
• 4:11
  monitored, even when the intent is security. It forces us to ask
• 4:14
  if the systems we build to protect users are actually
• 4:17
  fragmenting their experience by adding invisible layers of
• 4:20
  friction. We need to consider whether this kind of
• 4:23
  surveillance, however benign it seems, erodes the trust that
• 4:26
  good design is supposed to build. Over on r/ProductDesign,
• 4:29
  someone is challenging the notion that the first version of
• 4:32
  a product needs to be polished, arguing that iteration and
• 4:35
  consistency matter far more than initial perfection. The
• 4:37
  discussion compares various design tools, noting that their
• 4:40
  strength lies in adapting to new features rather than creating a
• 4:44
  flawless start. This is a vital reminder that our obsession with
• 4:47
  a perfect launch often blinds us to the messy, necessary work of
• 4:50
  refinement. It connects back to that initial theme, suggesting
• 4:53
  that we should stop trying to make systems look organized from
• 4:57
  day one and instead focus on making them resilient enough to
• 5:00
  handle the chaos of real user behavior. Today's discussions
• 5:03
  suggest that we're moving away from chasing surface-level
• 5:06
  polish and toward understanding the deeper, often messy,
• 5:09
  mechanics of how users actually interact with our systems.
• 5:19
  Chicago Camps is hosting Leadership By Design on Thursday
• 5:22
  & Friday, September 17 & 18. It's an online event, so you can
• 5:25
  join from anywhere in the world! Tickets are free, thanks to the
• 5:28
  generosity of the community! If it's within your budget, you can
• 5:31
  purchase a general admission ticket for only twenty six
• 5:34
  dollars - with limited early bird tickets at only fifteen
• 5:37
  dollars. Get tickets now at Chicago Camps dot org.
• 5:47
  Fabricio Teixeira argues that AI is exposing a craft crisis
• 5:49
  because we're trading human nuance for quantitative
• 5:52
  futurism. He says we need a researcher in the loop to keep
• 5:54
  ethics visible. But looking at the r/hci thread where that
• 5:57
  student struggles to bridge CS and cognitive science, I think
• 6:00
  the problem is deeper than just adding a researcher. It's a
• 6:03
  structural failure in how we define the work itself. That's
• 6:05
  exactly it. The student isn't just asking for a resume
• 6:08
  template. They're asking how to be fluent in two languages that
• 6:11
  our industry keeps treating as separate. We want engineers who
• 6:14
  understand human behavior and designers who understand system
• 6:16
  constraints. But our hiring practices still silo these
• 6:19
  skills. So we end up with tools like the date picker in
• 6:21
  r/UserExperience, where we debate whether to show a red
• 6:24
  error icon or disable the field, instead of asking why the input
• 6:27
  model is so fragile in the first place. Right. The date picker
• 6:30
  debate is a symptom. We're fighting over pixels while the
• 6:33
  underlying logic is broken. Teixeira warns that trusting the
• 6:35
  model more than the method hides the real user journey. If we
• 6:38
  can't even agree on how to handle a simple validation state
• 6:41
  without creating friction, how do we expect to govern complex
• 6:44
  AI systems? The legibility gap widens when we dismiss small
• 6:46
  samples of human struggle in favor of clean data. But
• 6:49
  dismissing that struggle is the wrong move. We shouldn't design
• 6:52
  out the possibility of error by disabling fields. That's
• 6:54
  paternalistic. We should design for correction. If a user enters
• 6:57
  an invalid date, the system should help them fix it, not
• 7:00
  block them. That requires empathy, which is the cognitive
• 7:03
  science part of that student's major. We need practitioners who
• 7:06
  can articulate why a specific interaction pattern fails, not
• 7:08
  just which component to drag onto the canvas. So the path
• 7:11
  forward isn't just better tools. It's better vocabulary. Yes.
• 7:14
  Until we stop treating technical skill and human understanding as
• 7:17
  separate competencies, we'll keep building systems that look
• 7:20
  organized to us but feel fragmented to everyone else.
• 7:24
  That's The Feed and The Thread for today. We'll catch you next
• 7:27
  time!