I remember watching the original "clojure" talks during Christmas break too.
At least it's a found memory that I keep, as opposed to all the troubles getting a somehow functioning clojure dev environment set up back in the day... For all my whining, it has actually got better nowadays, although I still don't know if it's acceptable to use lein as opposed to boot as opposed to deps.edn as opposed to [insert tool].
I don't think I'll ever professionally work on a things where the costs of clojure (training / mental reshaping / startup performances / etc...) will be worth the benefits (using a map of tuple to sets of immutable records and solve a gnarly problem in 10 lines and 50 parens.)
But as other said, the sermons _do_ change how you program in any language.
(I just wish I understood what in meant in "Effective Programs" by "typos are not important". They are, aren't they ? A typo is a runtime error begging to occur during the demo, how is that "not important" ? Never mind.)
I would advise to immediately go watch anything from Muratori or Blow to get the exact opposite perspective, pounder the fact that they are _both_ right and wrong in their own ways.
And go back to writing typescript like everyone.