How it at all related to let's say programming?
Well, for example learning vim-navigation or Lisp or a language with an advanced type system (e.g. Haskell) can be umwelt-transformative.
Vim changes how you perceive text as a structured, navigable space. Lisp reveals code-as-data and makes you see programs as transformable structures. Haskell's type system creates new categories of thought about correctness, composition, and effects.
These aren't just new skills - they're new sensory-cognitive modalities. You literally cannot "unsee" monadic patterns or homoiconicity once internalized. They become part of your computational umwelt, shaping what problems you notice, what solutions seem natural, and even how you conceptualize everyday processes outside programming.
It's similar to how learning music theory changes how you hear songs, or how learning a tonal language might affect how you perceive pitch. The tools become part of your extended cognition, restructuring your problem-space perception.
When a Lisper says "code is data" they're not just stating a fact - they're describing a lived perceptual reality where parentheses dissolve into tree structures and programs become sculptable material. When a Haskeller mentions "following the types" they're describing an actual sensory-like experience of being guided through problem space by type constraints.
This creates a profound pedagogical challenge: you can explain the mechanics of monads endlessly, but until someone has that "aha" moment where they start thinking monadically, they don't really get it. It's like trying to explain color to someone who's never seen, or echolocation to someone without that sense. That's why who's never given a truthful and heartfelt attempt to understand Lisp, often never gets it.
The umwelt shift is precisely what makes these tools powerful - they're not just different syntax but different ways of being-in-computational-world. And like the bat's echolocation, once you're inside that experiential framework, it seems impossible that others can't "hear" the elegant shape of a well-typed program.
There are other umwelt-transforming examples, like: debugging with time-travel/reversible debuggers, using pure concatenative languages, logic programming - Datalog/Prolog, array programming, constraint solvers - SAT/SMT, etc.
The point I'm trying to make - don't try to "understand" the cons and pros of being a bat, try to "be a bat", that would allow you to see the world differently.