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

Transcript

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

• 0:00
  Large language models aren't failing because they lack
• 0:02
  intelligence. Then what's actually causing all those
• 0:05
  errors? It's a total failure in how they manage context. So the
• 0:09
  tool is smart, but it just forgets the story. Exactly, and
• 0:12
  that's where the real design challenge begins.
• 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:26
  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
  Why do smart systems fail so often? It's not a lack of
• 0:47
  intelligence. It's a failure of context. Connor Joyce argues
• 0:51
  that Large Language Models produce confident but wrong
• 0:54
  answers because they lack situational constraints. In
• 0:57
  "Context matters… A lot" at UX Design.cc, he reframes this as a
• 1:00
  design problem of curating information. Models fill gaps
• 1:03
  with plausible assumptions when faced with choice overload. That
• 1:07
  rewrites the assumption that AI errors are purely technical
• 1:10
  limitations. True excellence often lives in details users
• 1:14
  never consciously notice. Edoardo Lunardi reflects on a
• 1:17
  decade of frontend work where code quality directly influences
• 1:20
  experience. He makes this case in "Where Engineering Meets
• 1:23
  Craft: Edoardo Lunardi’s Obsession with the Details" at
• 1:27
  Codrops, calling high-quality engineering a form of craft. The
• 1:30
  invisible work builds the trust that separates good products
• 1:33
  from great ones. You can now create complex organic shapes
• 1:37
  using pure CSS without relying on SVG assets. Temani Afif
• 1:40
  explains the math behind chaining curve commands for
• 1:43
  smooth continuity. In "Making Complex CSS Shapes Using
• 1:46
  shape()" at CSS-Tricks, he shares custom generators that
• 1:49
  automate the heavy lifting. This allows designers to adjust
• 1:52
  variables and produce unique code directly in the browser.
• 1:56
  Other reads today include I Love Typography on the history of
• 1:59
  dust jackets and UX Design.cc on terminal workflows and
• 2:02
  leadership in design.
• 2:11
  Welcome back to the Thread, where we talk about the messy
• 2:14
  reality of our daily work. Over on r/UXDesign, people are asking
• 2:17
  if naming your layers is actually a best practice or just
• 2:21
  a habit we never broke. It forces us to ask if our file
• 2:24
  hygiene is for our future selves or just to satisfy a manager.
• 2:27
  That discipline often separates a quick prototype from a handoff
• 2:31
  ready for production. In r/UXDesign again, the real
• 2:33
  question is whether anyone still cares about the design system at
• 2:37
  all. It reveals a tension between the promise of
• 2:40
  efficiency and the daily friction of rigid constraints.
• 2:43
  If the system feels like a wall, teams will just ignore it to
• 2:46
  ship faster. Over on r/UXDesign, someone realized
• 2:49
  Quora might hold the crown for the worst social media user
• 2:52
  experience. It highlights how feature bloat can bury the core
• 2:56
  value of reading and answering questions. When the interface
• 2:59
  fights the content, users simply leave the platform. In
• 3:02
  r/UXResearch, a professional is wondering if being reassigned to
• 3:05
  a new Meta recruiter after a long delay is a good sign. It
• 3:09
  shows how hiring volatility can leave researchers feeling like
• 3:12
  commodities rather than partners. You've to wonder if
• 3:15
  the delay meant the role was paused or the process is just
• 3:18
  broken. Over on r/UXDesign, folks are sharing notes on how
• 3:22
  we can finally improve our craft as a whole. The discussion moves
• 3:25
  past tools and tactics to focus on the actual thinking that
• 3:28
  drives better outcomes. It suggests the field is maturing
• 3:32
  past the hype cycle of new software. Today's topics show
• 3:35
  we're tired of shiny objects and ready to demand substance from
• 3:38
  our tools and our teams.
• 3:47
  Chicago Camps is hosting UX Camp Summer on Saturday, May 30th.
• 3:50
  There's an open call for speakers so submit your idea
• 3:52
  today! It's an online event, so you can join from anywhere in
• 3:55
  the world! Tickets are free, thanks to the generosity of the
• 3:58
  community! If it's within your budget, you can purchase a
• 4:01
  general admission ticket for only thirteen dollars and fifty
• 4:04
  cents. Get tickets now at Chicago Camps dot org.
• 4:13
  Connor Joyce argues that AI errors aren't technical failures
• 4:16
  but a lack of situational constraints. Models fill gaps
• 4:19
  with plausible assumptions when faced with choice overload,
• 4:22
  which reframes the problem as one of information curation
• 4:25
  rather than pure intelligence. That's the exact friction point
• 4:28
  I see in the design system discussions where teams ignore
• 4:30
  rigid constraints to ship faster. If the system feels like
• 4:33
  a wall instead of a guide, people will just bypass it to
• 4:36
  solve the immediate problem. And that connects to the CSS
• 4:39
  shape work where Temani Afif automates the heavy lifting so
• 4:41
  designers can adjust variables directly. When we remove the
• 4:44
  friction of execution, we free up mental space to actually
• 4:47
  think about the constraints that matter. But automation only
• 4:50
  works if the underlying logic is sound, otherwise we're just
• 4:53
  generating garbage at scale. The Quora example shows what happens
• 4:56
  when feature bloat buries the core value because the interface
• 4:59
  fights the content. So the failure isn't the tool or the
• 5:02
  lack of intelligence, it's a failure of context in how we
• 5:05
  structure those environments. We need to stop treating AI as a
• 5:08
  magic box and start treating it as a system that needs curated
• 5:11
  inputs to produce useful outputs. Right, and that means
• 5:13
  the real shift is moving from building features to curating
• 5:16
  the conditions where those features actually serve a
• 5:19
  purpose. The gap between a smart system and a useful one is
• 5:21
  no longer about code quality, it's about how well we define
• 5:24
  the boundaries of the problem. Exactly. And the teams that
• 5:27
  master those boundaries will be the ones turning complexity into
• 5:30
  clarity.
• 5:33
  That's The Feed and The Thread for today. We'll catch you next
• 5:36
  time!