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

Transcript

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

• 0:00
  Getting good at your job might be stopping you from getting
• 0:02
  better. So the skills are fine, but the work is just too easy.
• 0:06
  Exactly. We have to hunt for harder problems to keep growing.
• 0:13
  Welcome to The Feed and The Thread, brought to you by
• 0:15
  Chicago Camps. The Feed & The Thread is available online at
• 0:18
  feed and thread dot com to submit your feeds, or download
• 0:20
  our app for all the feeds and threads delivered right to your
• 0:23
  pocket.
• 0:31
  There's a strange comfort in repetition. We see it in how our
• 0:34
  brains process reality, how we build intelligence, and how we
• 0:37
  stagnate in our careers. Today's Feed asks why we keep using the
• 0:41
  same blocks, and whether that's a strength or a trap. Luke
• 0:44
  Wroblewski at LukeW's blog draws a parallel between brain
• 0:47
  architecture and AI in "Building Blocks for Intelligence". He
• 0:50
  argues that both systems rely on a single, repeated building
• 0:53
  block - cortical columns in the brain and transformer blocks in
• 0:56
  AI - that process information by combining "what" with "where."
• 1:00
  In the brain, these columns vote to reach a consensus on reality,
• 1:03
  while in AI, attention mechanisms allow tokens to share
• 1:06
  information to settle on an interpretation. This suggests
• 1:09
  that true intelligence isn't about complexity, but about how
• 1:12
  simple units combine context to form meaning. Dora Czerna
• 1:15
  writes about the danger of competence in "How getting good
• 1:19
  at your job can stop you getting better" at UX Design.cc. The
• 1:22
  core point is that getting good at your job often means getting
• 1:25
  assigned problems that are too easy or repetitive. This creates
• 1:28
  a comfort zone that halts further development, because
• 1:31
  routine tasks, even when performed with high proficiency,
• 1:34
  don't drive learning. Growth depends on the nature of the
• 1:37
  challenges we're given. Wira Indra Kusuma critiques newsroom
• 1:41
  visualization practices in "Borrowed slopes" at UX
• 1:43
  Design.cc. The piece argues that using generic, pre-existing data
• 1:47
  templates often leads to misleading representations,
• 1:49
  specifically when traffic lines bend or change direction. This
• 1:53
  approach prioritizes speed over accurate, context-rich
• 1:56
  communication, alienating the readers who need clarity the
• 1:59
  most. We're trading truth for convenience every time we apply
• 2:02
  a standard chart to a unique story. Other reads available
• 2:05
  from UX Design.cc on the multiple meanings of the color
• 2:08
  orange.
• 2:16
  Today's discussions circle a single, quiet question: why do
• 2:19
  we keep returning to the same familiar shapes, whether in
• 2:22
  code, in space, or in our own creative habits? It's a test of
• 2:25
  whether repetition is a foundation we build on, or a
• 2:28
  ceiling we stop at. Over on r/UI_Design, a developer is
• 2:31
  asking why users download their inventory app, Storagemagus, and
• 2:34
  then simply never come back. They've shared a full
• 2:37
  walkthrough of the onboarding, yet the silence afterward
• 2:40
  represents the core issue. This is the friction between first
• 2:43
  interest and daily habit. If the first step doesn't feel like the
• 2:46
  most obvious next step, the user leaves. Retention isn't about
• 2:50
  how good the app looks on day one, but whether it solves a
• 2:53
  problem fast enough to become invisible. In r/Design, someone
• 2:56
  posted a visual history of how presidents have redesigned the
• 2:59
  Oval Office over the decades. The question isn't about
• 3:02
  politics, but about how we curate identity in a shared
• 3:05
  space. Each redesign is a statement of what leadership
• 3:08
  should feel like at that moment. It reminds us that even the most
• 3:11
  established interfaces need periodic re-evaluation to stay
• 3:15
  aligned with the people using them. Also in r/Design, a
• 3:18
  designer turned a simple tree photograph into a minimalist
• 3:21
  movie poster titled The Shadows. They're asking if the
• 3:24
  composition evokes mystery without adding too many
• 3:26
  elements. This is a study in restraint. Sometimes the most
• 3:29
  powerful design choice is knowing what to leave out,
• 3:32
  trusting that the viewer will fill the gaps with their own
• 3:35
  experience. In r/UI_Design, a creator built a custom bookmark
• 3:38
  manager because they were tired of how browser bookmarks feel.
• 3:42
  They want feedback on the dashboard layout and navigation.
• 3:45
  This is a direct pushback against outdated interfaces that
• 3:48
  prioritize function over feel. When a tool feels clunky, we
• 3:51
  build our own. That isn't just frustration, it's a signal that
• 3:54
  the current standard hasn't kept up with how we actually think.
• 3:58
  Finally, in r/UI_Design, a designer redesigned a fitness
• 4:01
  app landing page, specifically asking for feedback on
• 4:04
  typography and hierarchy. They stated a clear preference for
• 4:07
  clarity over originality. This is a healthy reminder that in
• 4:10
  UX, the goal isn't to be surprising, but to be
• 4:12
  understood. If the user has to work to find the value
• 4:15
  proposition, the design has failed its primary job. These
• 4:18
  threads all point to the same place: we're constantly
• 4:21
  balancing the comfort of the familiar with the need to break
• 4:24
  through, and the best design is the one that makes that
• 4:27
  transition seamless.
• 4:36
  The Feed and The Thread is brought to you by Chicago Camps.
• 4:38
  For a weekly and monthly exploration of the patterns and
• 4:41
  signals across UX, you can also check out Patterns and Signals
• 4:44
  at the website patterns and signals dot com. Chicago Camps
• 4:47
  will have more events in 2027. You can submit to be a speaker
• 4:50
  at a future event at Chicago Camps dot org.
• 5:00
  I keep coming back to Wira Indra Kusuma's point about "borrowed
• 5:03
  slopes." It's not just that generic templates look lazy;
• 5:05
  it's that they actively lie. When you force a unique story
• 5:08
  into a standard chart, you're prioritizing speed over truth,
• 5:11
  and that's a failure of communication. I hear that, and
• 5:13
  I agree that the visuals are misleading. But I think the
• 5:16
  deeper issue is the comfort of repetition itself. We keep using
• 5:19
  the same blocks because they're safe. And that safety is exactly
• 5:22
  what stops us from growing. If we're just filling slots, we're
• 5:25
  executing tasks rather than solving problems. That connects
• 5:28
  directly to Dora Czerna's piece on competence. She argues that
• 5:31
  getting good at your job often means getting assigned problems
• 5:33
  that are too easy. So the system rewards you for being inventive.
• 5:37
  You become a machine that processes data, rather than a
• 5:39
  person who interprets it. And that's where it gets tricky. If
• 5:42
  we stop using the standard blocks, we risk slowing down the
• 5:45
  whole workflow. But if we keep using them, we stagnate. I think
• 5:48
  we need to stop treating efficiency as the highest value.
• 5:50
  We need to measure the quality of the insight. I see the
• 5:53
  tension there. You want to value the insight, but the tools we
• 5:56
  have are built for speed. So we're stuck in a loop where the
• 5:59
  infrastructure pushes us toward convenience, even when we know
• 6:02
  it's harmful to the reader. Yes, but we can break that loop.
• 6:05
  We can start by asking a different question during our
• 6:07
  reviews. Instead of asking if the chart is clean, we ask if
• 6:10
  the story is clear. If the answer is no, we stop. We accept
• 6:13
  the slower process because the clarity is worth the time. I
• 6:15
  think that's the shift we need. We have to treat the refusal to
• 6:18
  use a generic template as a feature, not a bug. It's a
• 6:21
  signal that we're doing the hard work of understanding the data,
• 6:24
  rather than just displaying it. Exactly. The test isn't whether
• 6:27
  the chart looks finished, it's whether the reader actually
• 6:30
  understands it.
• 6:32
  That's The Feed and The Thread for today. We'll catch you next
• 6:35
  time!