Latest / The Feed & The Thread / The Feed & The Thread - July 17, 2026

Transcript

The Feed & The Thread - July 17, 2026 · The Feed & The Thread

• 0:00
  AI just proved design is mostly just interface production.
• 0:03
  That's a brutal take on our last decade. If the machine can do it
• 0:06
  faster, what's left for us to actually do?
• 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:24
  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:32
  delivered right to your pocket.
• 0:41
  We traded strategic influence for delivery speed, and now that
• 0:44
  speed is automated. The question isn't whether we can produce
• 0:48
  interfaces faster, but whether we still know why we're building
• 0:51
  them. Jessa Parette at UX Design.cc makes a sharp case in
• 0:54
  "AI just called design’s bluff": AI has exposed that much
• 0:57
  professional design work was just interface production all
• 1:00
  along. She argues that design leadership voluntarily traded
• 1:04
  deep judgment for salary bands and agile velocity, prioritizing
• 1:07
  output over the harder conversations that define real
• 1:10
  value. That rewrites the assumption that our role is safe
• 1:13
  because it's creative. Instead, it suggests we made ourselves
• 1:16
  vulnerable by neglecting the systemic thinking that AI can't
• 1:19
  template. Victor Ayomipo challenges a sacred cow at
• 1:22
  Smashing Magazine in "When It Makes Sense To “Block” The Main
• 1:26
  Thread". He argues that blocking the main thread is sometimes
• 1:29
  faster than offloading tasks to background workers, because the
• 1:32
  serialization required to move data between isolated memory
• 1:36
  spaces is itself a blocking operation. This counters the
• 1:39
  instinct to always use Web Workers for performance, showing
• 1:42
  that large data transfers can freeze the UI longer than
• 1:45
  processing them directly. It's a reminder that performance rules
• 1:48
  have hidden costs. Usman Writes outlines six principles at UX
• 1:52
  Planet in "The 6 UX Principles That You Can Reduce User
• 1:55
  Frustration When Filling Out Forms" to reduce the friction of
• 1:58
  form filling. He focuses on small, intentional changes like
• 2:01
  simplifying input fields and providing immediate feedback to
• 2:04
  lower cognitive load. The goal is to transform a typically
• 2:07
  negative interaction into a smooth one by aligning the form
• 2:11
  structure with user expectations. It's practical
• 2:13
  evidence that reducing error rates starts with respecting the
• 2:16
  user's attention, not just validating their input. Other
• 2:20
  reads today from Codrops on Three.js speakers, CSS-Tricks on
• 2:23
  pointer events, and UX Design.cc on the SAID framework.
• 2:33
  Designers are hitting the ceiling of automated speed and
• 2:36
  realizing that producing interfaces faster doesn't
• 2:39
  automatically mean understanding why we're building them. Over
• 2:42
  on r/UI_Design, a designer is frustrated by the friction of
• 2:45
  fine-tuning browser-based UIs with AI coding tools. They want
• 2:49
  a Figma-like visual adjuster for minor properties like font size,
• 2:52
  but the current workflow forces context switching. It reveals a
• 2:56
  gap in our tooling: we can generate code instantly, but we
• 2:59
  still lack the tactile, real- time control that defines
• 3:02
  strategic refinement. If we can't easily tweak the details,
• 3:05
  we lose the ability to argue for specific design decisions. In
• 3:08
  r/UserExperience, a researcher is recruiting for a usability
• 3:11
  study on a comparison site, offering twenty-five dollars for
• 3:15
  thirty minutes of screen sharing. It's a standard
• 3:17
  request, but it highlights how manual observation remains the
• 3:21
  gold standard for understanding user intent. We can automate the
• 3:24
  interface, but we still need humans to tell us if the mental
• 3:27
  model holds up. The compensation is modest, but the insight is
• 3:31
  irreplaceable. Over on r/UI_Design, someone went heavy
• 3:34
  on scroll animations for a landing page and is asking if
• 3:37
  the motion helps or hinders the experience. It's the classic
• 3:40
  tension between visual flair and content hierarchy. Animations
• 3:43
  can guide the eye, but they often distract from the core
• 3:46
  message. The question isn't just about aesthetics; it's about
• 3:49
  whether the motion serves the user's goal or just the
• 3:52
  designer's ego. In r/UI_Design, a designer shared their puzzle
• 3:56
  game, CrossLines, which prioritizes zero friction by
• 3:59
  removing signups and ads. They're asking for blunt
• 4:01
  feedback on rule clarity and fairness. It's a mature
• 4:04
  approach: lowering barriers to entry is often more valuable
• 4:07
  than polishing visuals. The focus on usability over
• 4:10
  marketing fluff shows a shift toward respecting the user's
• 4:13
  time and attention. Over on r/UI_Design, another designer
• 4:16
  used Gaussian Splatting to create a 3D laptop scan for a
• 4:19
  landing page, questioning if the interactive gesture is too
• 4:22
  distracting. It's a high- fidelity experiment that risks
• 4:25
  burying the core content under novelty. The tension here's
• 4:29
  clear: technical wow factor often comes at the cost of
• 4:31
  functional clarity. We need to ask if the innovation actually
• 4:35
  improves the user's journey or just impresses other designers.
• 4:38
  We're building faster than ever, but we're struggling to justify
• 4:42
  the design choices that make those interfaces worth using.
• 4:52
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:55
  & Friday, September 17 & 18. It's an online event, so you can
• 4:58
  join from anywhere in the world! Tickets are free, thanks to the
• 5:01
  generosity of the community! If it's within your budget, you can
• 5:04
  purchase a general admission ticket for only twenty six
• 5:07
  dollars - with limited early bird tickets at only fifteen
• 5:09
  dollars. Get tickets now at Chicago Camps dot org.
• 5:19
  Victor Ayomipo's argument that blocking the main thread can
• 5:22
  sometimes be faster than using Web Workers flips the standard
• 5:25
  performance playbook. The serialization cost of moving
• 5:27
  data between isolated memory spaces is often higher than just
• 5:30
  processing it directly, which means our instinct to offload
• 5:33
  everything to background workers is actually creating more
• 5:36
  friction. That makes total sense when you look at the
• 5:39
  r/UI_Design thread about AI coding tools. We're generating
• 5:41
  code instantly, but we lack the tactile control to tweak those
• 5:44
  minor properties like font size without breaking the flow. If
• 5:47
  the tooling forces constant context switching, we lose the
• 5:50
  ability to argue for specific design decisions because the
• 5:53
  refinement process is too painful. Exactly. The AI
• 5:55
  tooling exposes a gap in our workflow where we can produce
• 5:58
  interface components quickly, but we can't easily justify the
• 6:01
  strategic choices behind them. It connects back to the main
• 6:04
  thread issue because both are about hidden costs. The cost
• 6:06
  isn't just the compute time or the generation speed, it's the
• 6:09
  cognitive load of managing the handoff between high-level
• 6:12
  intent and low-level execution. But I see it differently. The
• 6:15
  issue isn't just the handoff. It's that we're treating design
• 6:18
  as a production step rather than a judgment call. If we can't
• 6:21
  easily tweak the details, we stop asking why those details
• 6:24
  matter. The risk is that we accept the AI's output because
• 6:26
  it's fast, rather than refining it because it's right. We need
• 6:29
  to rebuild the muscle for strategic refinement, not just
• 6:32
  faster production. So the bottleneck isn't the technology.
• 6:35
  It's our incentive structure. We reward speed over precision
• 6:38
  because the tools make speed easy and precision hard. If we
• 6:41
  don't change how we measure success, we'll just keep trading
• 6:43
  deep judgment for salary bands and faster, emptier interfaces.
• 6:46
  Right. And that's why the next wave of tools needs to
• 6:49
  prioritize real-time control over raw generation speed. We
• 6:52
  don't need another way to dump code. We need a way to feel the
• 6:55
  interface change as we think about it. The value isn't in the
• 6:58
  output. It's in the argument for why that output works. The gap
• 7:01
  between uncomfortable and obsolete is exactly where the
• 7:03
  most interesting work has always lived. And right now, that gap
• 7:06
  is wide open for anyone willing to defend the details.
• 7:11
  That's The Feed and The Thread for today. We'll catch you next
• 7:14
  time!