Latest / The Feed & The Thread / The Feed & The Thread - August 7, 2026

Transcript

The Feed & The Thread - August 7, 2026 · The Feed & The Thread

• 0:00
  Star Trek got AI wrong because language is the easy part. So
• 0:03
  the hard part is actually the thinking? Exactly, and that
• 0:06
  backward vision explains why our current AI tools feel fluent but
• 0:10
  fundamentally broken.
• 0:15
  Welcome to The Feed and The Thread, brought to you by
• 0:17
  Chicago Camps. Leadership By Design is on Thursday and
• 0:20
  Friday, September 17 and 18 and tickets are available now! And
• 0:23
  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:33
  delivered right to your pocket.
• 0:42
  We built tools to remove friction, but now that friction
• 0:45
  is gone, we're left with a mess of low-effort noise and systems
• 0:49
  that lie to us with confidence. Patrick Neeman at UX Design.cc
• 0:53
  challenges sci-fi's timeline in "What Star Trek got wrong about
• 0:56
  AI (so far)". He points out that fluent language arrived cheap
• 1:00
  and fast, while honest, physical reliability remains elusive. Our
• 1:03
  current models are sycophantic, flattering users even when
• 1:07
  they're wrong, which means we've gained speed but lost truth.
• 1:10
  Pavel Samsonov calls it cognitive pollution in
• 1:13
  "Cognitive Pollution: Real knowledge only forms through
• 1:16
  doing the work", published on Product Picnic. He argues that
• 1:20
  AI-generated templates create a burden for readers who must
• 1:23
  filter out the lack of genuine thought. This isn't efficiency,
• 1:27
  it's disrespect for the time it takes to process empty words.
• 1:30
  The piece in "The Hidden Compliance Challenge in Global
• 1:33
  Payroll UX" on UX Planet tackles global payroll compliance. It
• 1:37
  shows how blind consent boxes fail users by mixing mandatory
• 1:40
  legal data with optional sharing. Separating these
• 1:43
  requirements improves trust and accuracy, proving that clarity
• 1:47
  is a compliance feature, not just a nice-to-have. Other
• 1:50
  articles today from I Love Typography on Zinkraft, Codrops
• 1:53
  on WebGPU experiments, and CSS- Tricks on the 2026 developer
• 1:57
  survey.
• 2:04
  Designers are asking the same question from five different
• 2:07
  angles today: what actually counts as proof when the work
• 2:10
  itself becomes harder to point to. Over on r/UXDesign, someone
• 2:14
  is asking how to generate motion graphics for their portfolio
• 2:17
  using AI, specifically to bridge the gap in animation skills.
• 2:20
  It's a practical problem, but it points to a deeper tension. We
• 2:23
  built tools to remove the friction of learning complex
• 2:26
  software, yet now we're left with low-effort assets that
• 2:29
  might not reflect real capability. The so-what here's
• 2:32
  simple: if the barrier to entry disappears, the signal of skill
• 2:35
  gets buried in the noise. In the same subreddit, another
• 2:38
  designer is questioning how we mock up flows for AI agents,
• 2:41
  noting the frustration with verifying that shipped behaviors
• 2:44
  match intended outcomes. Traditional design relies on
• 2:47
  deterministic paths, but AI is infinite and unpredictable. This
• 2:50
  reveals a lack of standard processes for handling
• 2:53
  uncertainty. We need new ways to validate systems that lie to us
• 2:56
  with confidence, even when they're technically correct.
• 2:59
  There's also a thread questioning what prominent
• 3:01
  influencers like Tommy Geoco have actually shipped,
• 3:04
  contrasting their popularity with a lack of visible product
• 3:07
  delivery. It's a skeptical look at whether the industry
• 3:10
  prioritizes tutorial creation over actual product delivery.
• 3:13
  This matters because it challenges the value of clout
• 3:16
  versus tangible output. We're seeing a shift where visibility
• 3:19
  doesn't always equate to verified expertise. Someone
• 3:22
  also asked for feedback on Adrian Bilan's book Confident
• 3:25
  UX, seeking to debrief thoughts after reading. While there's no
• 3:28
  consensus yet, the request itself highlights a hunger for
• 3:31
  frameworks that help designers navigate ambiguity. It's not
• 3:34
  just about the book, but about finding anchors in a field
• 3:37
  that's moving too fast for traditional playbooks to keep
• 3:40
  up. Finally, in r/UI_Design, a user is exploring whether AI
• 3:43
  agents can handle version control for design files,
• 3:46
  drawing a parallel to developer repositories. It addresses the
• 3:49
  cumbersome nature of managing iterations in Figma. If AI can
• 3:52
  automate this, it removes another layer of friction, but
• 3:55
  we have to ask if we're optimizing for speed at the cost
• 3:58
  of intentionality. We're removing friction faster than
• 4:01
  we're building the systems to manage the resulting chaos, and
• 4:04
  that gap is where the real design work is happening now.
• 4:14
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:17
  & Friday, September 17 & 18. It's an online event, so you can
• 4:20
  join from anywhere in the world! Tickets are free, thanks to the
• 4:23
  generosity of the community! If it's within your budget, you can
• 4:26
  purchase a general admission ticket for only twenty six
• 4:29
  dollars - with limited early bird tickets at only fifteen
• 4:31
  dollars. Get tickets now at Chicago Camps dot org.
• 4:41
  Pavel Samsonov calls AI- generated templates cognitive
• 4:44
  pollution, and Patrick Neeman backs that up by pointing out
• 4:47
  that while fluent language arrived cheap, honest
• 4:49
  reliability didn't. We have speed without truth, which means
• 4:52
  the friction we removed was actually the quality control.
• 4:54
  That's the tension right there. The community is asking how to
• 4:57
  use AI to bridge skill gaps, like motion graphics, but
• 5:00
  they're hitting a wall because the output lacks that human
• 5:03
  judgment. It's not just about filling a portfolio gap, it's
• 5:06
  about realizing that low-effort assets don't prove competence,
• 5:09
  they just prove you have access to a tool. Exactly. The payroll
• 5:12
  UX article shows this too. When you mix mandatory legal data
• 5:15
  with optional sharing in a blind consent box, you're creating a
• 5:18
  system that lies by omission. Clarity is a compliance feature.
• 5:21
  If we let AI generate the interface without that rigorous
• 5:23
  separation of intent, we aren't being efficient, we're being
• 5:26
  negligent. So the designer's job isn't to make the flow
• 5:29
  faster, it's to make the intent undeniable. We're removing
• 5:32
  friction faster than we're building the systems to manage
• 5:34
  the resulting chaos, and that gap is where the real design
• 5:37
  work is happening now. We need to stop treating speed as the
• 5:40
  default metric for success. Agreed. The next standard isn't
• 5:43
  how fast you can ship, it's how clearly you can explain why the
• 5:46
  system works the way it does.
• 5:49
  That's The Feed and The Thread for today. We'll catch you next
• 5:52
  time!