I am a counterpoint myself, I don't consider myself a particularly experienced programmer, but I rarely encounter type errors, most of them are semantic or logic errors.

I'm faster at finding and solving the issues with languages I know best (not surprisingly) regardless of their static or dynamic nature.

Experience, in my case, is knowing where to look, being able to quickly parse an error message, from the compiler, the linter or the runtime, but most of all knowing the code base at heart.

When I confront a code base that is new for me, I feel lost, whatever paradigm has been used.

I simply don't know where to put my hands before I spent time reading and analyzing it.

The time required to understand it depends exclusively on the complexity of the project.

There hasn't been a single time where types have helped me (more than being able to grep the function signature) or their absence slowed me down.

JavaScript and TypeScript are great because you can compare them directly and they are essentially the same language, one with types.

And as someone who has written JS for over a decade, TS is hands down better, it’s not been close how much nicer it is to work in the latter. The bigger the project is the more it helps.

> TS is hands down better

Don't want to sound harsh, but it doesn't take much to be better than JS

You don't sound harsh, just uninformed and unable to make a counterargument.