That is good. I do not want to remember Java and Kotlin.
In any case, Java, and especially Kotlin are quite tolerable with IntelliJ. It is a great IDE for those two at least. Plus I get paid, which is also a motivator... :D
[1] Truth be told, it is difficult to keep that sanity because I dislike the OTP documentation. I am reading books instead. I already know what their "target_system" does anyway, I modified it a lot for my use case but I reverted it because I thought it would be more of a hassle in the end.
Plus, macros (basically, generators of code). How can you say no to that?
You will always have something that you don't know. Took me a loooong time to get over it. Try and short-circuit this struggle because it would otherwise never end.
I also have anxiety about my health when I notice something out of the place, but that is a different sort of issue. I remember when outside there were construction workers and beneath me the floor moved and I almost had a panic attack because of it. At first I did not know it was caused by them, I thought something was happening to me. It got better when I realized it was just them.
Doesn't that make it a little better?
I get what you mean with performance anxiety -- my last job kind of ended because I felt a severe impostor syndrome. But eventually it turned out it wasn't only that; I was forced into rituals and ways of work I didn't enjoy so the job couldn't possibly work. Realizing this instantly made me feel better.
Two and a half years ago I felt stuck working with only dynamic languages most of my career so I started learning Rust. Now I have an extremely powerful tool in my belt that solves problems that most dynamic languages cannot solve [adequately].
But I'm not going to learn yet another dynamic language if that won't make me any money or expose me to a new way of thinking, no. Nor will I relearn C++.
Furthermore, if I make a comeback to JS then I'll prefer to learn TypeScript and pick the most productive tools for it (Parcel struck me as mostly getting out of the way).
I get the overall sentiment of the article even if it expresses it rather poorly.
It has a good point, though; many of us the programmers are rather capricious and spoiled and get distracted by new shinies -- as opposed to learning several skills deeply and be then very useful to the business we're serving.
We easily forget that we do what we do for money.