More Developer Tea episodes

Finding A Way Through Forced Change of AI Transformations thumbnail

Finding A Way Through Forced Change of AI Transformations

Published 14 Nov 2026

Duration: 00:18:00

Confronting fear of AI-driven changes through Stoic principles and stress adaptation helps engineers build resilience and navigate industry shifts effectively.

Episode Description

You likely chose most of the changes in your career yourself, and many engineers now feel AI-driven change is being forced on them. In this episode, I...

Overview

The episode explores how software engineers have historically experienced professional growth through self-directed learning and choice, describing a period when engineers had significant agency in picking technologies and roles. The speaker frames this as a source of pride and identity, noting that learning new skills felt like gaining "superpowers" and that the craft itself became deeply personal.

The discussion then shifts to the current industry transformation driven by AI and agentic engineering. The speaker addresses engineering managers, urging them to understand that code has become an emotional attachment comparable to a blacksmith's long-used hammer, and that "a purely rational argument that tooling is better and therefore you should pick it" misses the human dimension of the transition.

The episode proposes a framework drawing on stoic philosophy, specifically the idea that "the obstacle is the way rather than the obstacle being in the way," reinforced by Nicholas Taleb's concept of anti-fragility and the biological cycle of "stress, adaptation, recovery, repeat." The speaker encourages engineers facing fear of change to pause, identify what they are avoiding, and confront it deliberately, arguing that "our avoidance mechanisms tend to make things worse" while safe exposure allows adaptation and resilience to develop.

What If

  • What if you treated your fear of adopting agentic tooling as a stressor in a stress-adaptation-recovery cycle?

    • Move: Set aside a fixed 30-minute block this week to use an AI coding assistant on a small, low-stakes task (a script, a test file), then stop and journal what you felt.
    • Why Now? The speaker notes that "our avoidance mechanisms tend to make things worse" and that "business is changing very rapidly as a result of this stuff" with no sign of reversal.
    • Expected Upside: You may discover, as the CBT reference suggests, that "the thing that you feared, you were able to survive," building a baseline of resilience before pressure intensifies. (Proposal, not a guaranteed outcome.)
  • What if you approached a new technology the way the speaker approached jQuery animations - by publishing what you learn rather than waiting to master it?

    • Move: Pick one agentic workflow, use it on a real project, and write a short blog post or podcast segment describing what surprised you, what broke, and what you would do differently.
    • Why Now? The speaker describes how "picking up jQuery animations was one of the first things that I learned that really opened my eyes to what I could make, what I could publish for the world to see."
    • Expected Upside: You convert a stressful adaptation into a visible artifact, turning the "obstacle" into a "way" forward and creating a reference point for future changes. (Possibility, not a source fact.)
  • What if you, as a solo developer, built a personal recovery protocol before your next forced tooling change?

    • Move: Define in writing what your recovery looks like after a stressful adaptation - a day off coding, a walk, a conversation with a peer - so that when a new mandate lands, you already have the "proper recovery" the speaker says adaptations require.
    • Why Now? The speaker stresses that "if you provide your body with the proper recovery then those adaptations, generally speaking, make you more resilient," and warns that without it the cycle breaks.
    • Expected Upside: You reduce the risk that a single stressful transition becomes a "debilitating fear" rather than a manageable stressor, preserving your capacity to keep building software. (Proposal.)

Takeaway

  • Pause and name what you are avoiding: "try to evaluate what about this shift, this industry shift, are you avoiding?" Write the answer down before deciding whether to engage.
  • Confront the fear in a bounded, safe way: pick one small task with the new tooling, time-box the session, and stop when the timer ends rather than when the fear does.
  • Build a recovery step into every adaptation cycle: after a stressful learning session, schedule deliberate rest so that "those adaptations, generally speaking, make you more resilient to whatever that original stressor was."
  • Publish or share what you learn to convert private stress into a public artifact, mirroring the speaker's use of a blog or podcast to process new skills.
  • If you lead engineers, lead with the emotional context first: recognize that code has become "a friend to us, something that has become an important favorite tool," and acknowledge the attachment before proposing the change.

Recent Episodes of Developer Tea

24 Oct 2026 Signs You May Have a Regressive Mindset

"Engineers must embrace continuous learning, avoid regressive mindsets like information avoidance and bias, and actively adapt to stay relevant in a fast-changing industry."

5 Sept 2026 You Don't Learn Helplessness - You Learn Control

"Recognizing and exerting control - even in small ways - rewires the brain to build resilience, confidence, and proactive behavior, countering learned helplessness and enabling progress in personal and professional challenges."

More Developer Tea episodes