Latest / The Feed & The Thread / The Feed & The Thread - October 20, 2026

Transcript

The Feed & The Thread - October 20, 2026 · The Feed & The Thread

• 0:00
  Forward deployed engineer roles jumped one thousand one hundred
• 0:03
  sixty five percent. So the job title is changing, not the work.
• 0:06
  It's about deep customer insight, and that's where
• 0:09
  designers still hold the edge.
• 0:14
  Welcome to The Feed and The Thread, brought to you by
• 0:17
  Chicago Camps. The Feed & The Thread is available online at
• 0:19
  feed and thread dot com to submit your feeds, or download
• 0:22
  our app for all the feeds and threads delivered right to your
• 0:25
  pocket.
• 0:32
  If we can generate code in seconds, why do we still need
• 0:36
  designers? The answer is about judgment. Fabricio Teixeira at
• 0:39
  UX Design.cc makes this clear in "Why design (still) matters,
• 0:42
  Taste is not a methodology, Borrowed slopes", noting a one
• 0:46
  thousand one hundred and sixty- five percent surge in forward-
• 0:49
  deployed engineer roles. These positions prioritize deep
• 0:52
  customer immersion over pure technical execution. The
• 0:55
  argument is that taste is a critical differentiator against
• 0:58
  the sameness AI produces. Designers must define their
• 1:01
  value through decision rights and business coherence. The job
• 1:05
  now is this. Nick Babich at UX Planet tests this shift in "I
• 1:08
  Tried Designing an Entire Product in Claude Code Without
• 1:11
  Figma", designing an entire product in Claude Code without
• 1:15
  Figma. The point is that AI assistants are becoming capable
• 1:18
  design partners, generating functional UI through natural
• 1:21
  language. This moves the focus from static visual artifacts to
• 1:24
  interactive, code-based prototypes. It reduces the
• 1:27
  friction between design intent and functional reality. The
• 1:31
  workflow changes when the tool is the prototype. Jeffrey
• 1:34
  Zeldman steps away from the screen in "Now Playing: “Side
• 1:37
  Two”", announcing the release of his second instrumental album,
• 1:40
  Side Two. It features seventeen tracks spanning jazz-funk,
• 1:44
  electronica, and art rock. This highlights the creative range
• 1:47
  required in our field, moving beyond the interface into
• 1:50
  broader artistic expression. Design is about making culture.
• 1:53
  Other reads available from UX Design.cc on attention
• 1:56
  bottlenecks and the value of silence.
• 2:06
  Today's discussions circle a single, uncomfortable truth: in
• 2:09
  a market flooded with automated tools, the value of human
• 2:12
  judgment is under direct scrutiny. Over on r/UXResearch,
• 2:15
  a researcher with five years of experience, including time at
• 2:18
  major tech firms, is navigating eight months of unemployment.
• 2:21
  They note that the job market has shifted drastically compared
• 2:24
  to last year, where a similar search took less than three
• 2:27
  months. This disconnect between senior expertise and hiring
• 2:30
  velocity is a critical data point. It suggests that
• 2:33
  technical skills alone are no longer enough to secure a seat
• 2:36
  at the table. The so-what here's clear: practitioners must
• 2:39
  articulate the specific judgment calls they made, not just the
• 2:42
  tools they used. In r/Design, someone is wrestling with a
• 2:45
  question of identity after colleagues silently altered
• 2:48
  their work. They ask how one knows if they're a top-tier
• 2:51
  designer when their commercial output is deemed insufficient,
• 2:54
  even if personal projects receive praise. This tension
• 2:57
  between creative vision and commercial execution is a daily
• 3:00
  reality for many. It reveals a gap in how we define competence.
• 3:03
  The takeaway is that design isn't just about aesthetics, but
• 3:06
  about solving the right problem. If your work is constantly fixed
• 3:10
  by peers, the issue may not be your skill, but your alignment
• 3:13
  with the business goal. Also in r/Design, a student is asking
• 3:16
  for practical advice on how to handle moments when a design
• 3:19
  feels stuck. They want to know the specific triggers that lead
• 3:22
  to a block and the strategies practitioners use to diagnose
• 3:25
  the issue. This is a fundamental part of the craft, yet it's
• 3:29
  rarely taught explicitly. The so-what's that recognizing when
• 3:32
  a design isn't working is a skill in itself. It requires
• 3:35
  stepping back from the details to evaluate the underlying
• 3:38
  logic. This metacognitive ability is exactly what
• 3:40
  separates a proficient designer from a master. The common
• 3:43
  thread in these conversations is the shift from producing
• 3:46
  artifacts to exercising discernment. As tools become
• 3:49
  more accessible, the premium on knowing why you made a choice,
• 3:52
  rather than just how, becomes the defining metric of
• 3:55
  professional value.
• 4:03
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:06
  For a weekly and monthly exploration of the patterns and
• 4:09
  signals across UX, you can also check out Patterns and Signals
• 4:12
  at the website patterns and signals dot com. Chicago Camps
• 4:14
  will have more events in 2027. You can submit to be a speaker
• 4:17
  at a future event at Chicago Camps dot org.
• 4:27
  I've been sitting with the number from Fabricio Teixeira's
• 4:29
  piece on UX Design.cc. He cites a one thousand one hundred and
• 4:32
  sixty-five percent surge in forward-deployed engineer roles.
• 4:35
  That's a market signal that the industry is betting its future
• 4:38
  on people who can bridge the gap between deep customer immersion
• 4:41
  and technical execution. That specific number is what got me.
• 4:43
  It suggests that the market has already priced in the idea that
• 4:46
  generating code is the easy part. The hard part is the
• 4:49
  judgment call. Teixeira argues that taste is the differentiator
• 4:52
  against the sameness AI produces, and I think that's
• 4:54
  where the work lives. It's about who can look at the output and
• 4:57
  say, "this doesn't feel right." Exactly. And that judgment is
• 5:00
  what separates a functional artifact from a coherent
• 5:02
  product. When you look at Nick Babich's experiment of designing
• 5:05
  an entire product in Claude Code without Figma, you see the
• 5:08
  friction dropping between intent and function. But without the
• 5:10
  designer's hand steering the logic, you just get a very
• 5:13
  efficient version of the same thing. The tool removes the
• 5:16
  labor of construction, but it doesn't remove the need for
• 5:18
  direction. That's the crux of it. We're seeing this in the
• 5:21
  community threads too, where people are asking how to
• 5:23
  diagnose when a design feels stuck. That metacognitive
• 5:26
  ability, recognizing when the underlying logic is broken, is
• 5:28
  the skill that survives the automation. It's about having
• 5:31
  the intuition to know that the flow itself is wrong. So the
• 5:34
  value proposition shifts. It's about the quality of the
• 5:36
  decision. The forward-deployed engineer role exists because
• 5:39
  companies need someone who can translate a business constraint
• 5:42
  into a user-facing solution. That's a cognitive task. I'm
• 5:44
  ready to bet that the next decade of our field is defined
• 5:47
  by who can articulate that judgment clearly. The tools will
• 5:50
  keep getting faster, and the code will keep getting cleaner.
• 5:53
  But the ability to define what "good" looks like in a specific
• 5:55
  context, and to defend that choice, that's the work that
• 5:58
  remains.
• 6:00
  That's The Feed and The Thread for today. We'll catch you next
• 6:03
  time!