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

Transcript

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

• 0:00
  Your browser already does the heavy lifting. So why are we
• 0:02
  still shipping bloat? Because we keep ignoring native platform
• 0:06
  features that eliminate entire dependency chains. We have to
• 0:09
  look at what baseline support actually changes.
• 0:15
  Welcome to The Feed and The Thread, brought to you by
• 0:18
  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:26
  minute UX at five em UX dot com. The Feed & The Thread is
• 0:29
  available online at feed and thread dot com to submit your
• 0:32
  feeds, or download our app for all the feeds and threads
• 0:35
  delivered right to your pocket.
• 0:43
  We keep adding tools to our workflows, assuming complexity
• 0:47
  equals capability. But what if the real bottleneck isn't the
• 0:50
  technology itself, but how we measure its actual value against
• 0:53
  the work we already do? Caleb Sponheim at Nielsen Norman Group
• 0:57
  cuts through the noise in "How to Decide When an AI Tool Is
• 1:00
  Worth Keeping". He argues that adoption pressure isn't proof of
• 1:04
  utility. Instead, he introduces the PROVE framework, which tests
• 1:07
  one tool against one specific task. The goal is a defensible,
• 1:10
  provisional decision on whether the workflow actually improves.
• 1:14
  Most evaluations fail because teams don't compare AI output
• 1:17
  against their existing manual processes. You can't claim
• 1:20
  efficiency if you haven't measured the baseline. Jad
• 1:23
  Joubran at Smashing Magazine makes a sharp case in "How
• 1:26
  Baseline Can Help You Ship Less JavaScript". Many JavaScript
• 1:29
  dependencies are now redundant because browsers natively
• 1:33
  support features like date formatting and deep cloning. He
• 1:36
  points to Baseline, a project that categorizes feature
• 1:39
  availability across browsers. The author proposes a three-
• 1:42
  question framework to safely audit and remove libraries. This
• 1:45
  focuses on audience compatibility, swap costs, and
• 1:48
  feature parity. Treating dependencies in clusters helps
• 1:51
  you ship less code without breaking the experience. Oliver
• 1:54
  Meredith Cox at UX Design.cc explores this in "The cybernetic
• 1:58
  application". Current information systems often induce
• 2:01
  confusion because they lack the structural adaptability for
• 2:04
  complex human thought. Drawing on Stafford Beer's cybernetic
• 2:07
  principles, he defines variety as the capacity to handle
• 2:10
  environmental complexity. The core thesis is that writing apps
• 2:14
  fail because they don't support the high variety of cognitive
• 2:17
  needs. This leads to abandoned or duplicated work. We need
• 2:20
  systems that match the recursion of human thought, not just the
• 2:24
  linear flow of data. Other articles today from UX Planet on
• 2:27
  creating 3D objects with AI, Codrops on building the PX PUSH
• 2:30
  website, and CSS-Tricks on styling the dialog element.
• 2:40
  Designers are adding tools to their workflows, assuming
• 2:43
  complexity equals capability. But the real bottleneck might
• 2:47
  not be the technology itself. It's how we measure its actual
• 2:50
  value against the work we already do. Over on
• 2:52
  r/UserExperience, a researcher points out a critical gap in
• 2:55
  recording setups. The recording is solved, but synthesizing
• 2:59
  insights remains a major pain point. Current tools focus on
• 3:02
  clips rather than synthesis. The author critiques manual tagging
• 3:05
  as excessive. The tension here's whether we're optimizing for
• 3:08
  capture or for understanding. If we can't synthesize, the
• 3:11
  recording is just storage. In r/UI_Design, a designer
• 3:14
  struggles to create unique hero sections for a business
• 3:17
  registration firm. The goal is to interrupt the user's
• 3:20
  assumption that it's just another generic site. The
• 3:23
  difficulty lies in generating variations that feel fresh. This
• 3:26
  reveals a deeper issue with template-driven design. We often
• 3:29
  prioritize safety over distinctiveness. The so-what's
• 3:32
  that uniqueness requires risk, not just more options. Also in
• 3:36
  r/UI_Design, a post challenges Fitts's Law and Hick's Law on
• 3:39
  mobile devices. The author doesn’t quite understand the
• 3:42
  laws and claims these laws were written for mouse and cursor
• 3:45
  interfaces. They may not hold up on touch screens. The author
• 3:48
  notes that edge-based optimizations don't work the
• 3:51
  same way for fingers. This questions our reliance on
• 3:54
  desktop-era heuristics. We need to re-evaluate foundational laws
• 3:57
  for touch. Over on r/UXDesign, a designer worries that entry-
• 4:00
  level roles rely too heavily on AI tools. The concern is that AI
• 4:04
  provides quick answers but fails to teach critical reasoning.
• 4:07
  Newcomers may struggle to distinguish good design from
• 4:10
  bad. The tension is between speed and skill development. If
• 4:13
  we outsource thinking, we lose the ability to defend decisions.
• 4:17
  Finally, in r/UXDesign, a junior designer asks about CV titles.
• 4:20
  The choice is between Product Designer and Graphics and
• 4:23
  Product Designer. The core tension is seniority versus
• 4:26
  keyword density for applicant tracking systems. This
• 4:29
  highlights the performative nature of job hunting. We
• 4:31
  optimize for machines, not humans. The so-what's that our
• 4:34
  identities are becoming algorithmic inputs. We're
• 4:37
  measuring success by tool adoption and keyword matching,
• 4:40
  rather than by the quality of the thinking those tools enable.
• 4:51
  Chicago Camps is hosting Leadership By Design on Thursday
• 4:54
  & Friday, September 17 & 18. It's an online event, so you can
• 4:57
  join from anywhere in the world! Tickets are free, thanks to the
• 5:00
  generosity of the community! If it's within your budget, you can
• 5:03
  purchase a general admission ticket for only twenty six
• 5:06
  dollars - with limited early bird tickets at only fifteen
• 5:09
  dollars. Get tickets now at Chicago Camps dot org.
• 5:19
  The connection between Baseline and the PROVE framework is
• 5:22
  striking because both demand a measurable floor before you
• 5:24
  build up. Jad Joubran's argument for auditing JavaScript
• 5:27
  dependencies relies on knowing exactly what the browser already
• 5:30
  supports, while Caleb Sponheim insists you can't judge an AI
• 5:32
  tool unless you measure it against your existing manual
• 5:35
  process. Both are essentially arguing that we're optimizing
• 5:38
  for the wrong things because we haven't defined the baseline.
• 5:40
  That's the trap, isn't it. We're measuring success by tool
• 5:43
  adoption or keyword matching rather than the quality of the
• 5:46
  thinking those tools enable. We need to re-evaluate what the
• 5:48
  baseline even is. And that's where the cybernetic application
• 5:51
  piece by Oliver Meredith Cox becomes critical. He argues that
• 5:54
  our current systems lack the structural adaptability for
• 5:56
  complex human thought because they don't account for variety.
• 5:59
  If we're just swapping out a JavaScript library or an AI
• 6:02
  plugin without understanding the systemic complexity we're trying
• 6:05
  to manage, we're just adding noise. The problem isn't the
• 6:07
  tool, it's that we're treating complex adaptive systems like
• 6:10
  static machines. So we stop asking if the tool is fast and
• 6:12
  start asking if it actually reduces cognitive load. The
• 6:15
  researcher in r/UserExperience nailed this when pointing out
• 6:18
  that recording is solved but synthesis is the pain point.
• 6:20
  We're optimizing for capture instead of understanding. If we
• 6:23
  can't synthesize, the recording is just storage. The shift has
• 6:26
  to be from accumulating data to curating insight. It's a shift
• 6:29
  from volume to signal. We have to accept that most of what we
• 6:31
  capture is noise. Exactly. The value isn't in having the tool,
• 6:34
  it's in having the discipline to throw it away when it doesn't
• 6:37
  improve the workflow.
• 6:40
  That's The Feed and The Thread for today. We'll catch you next
• 6:43
  time!