I'm an indie maker, and a freelance developer via Toptal.
I'm currently working on Xebel, a community and mentorship platform to help online learners succeed. Check it out at xebel.co.
I always recommend using TypeScript with strict mode on, while avoiding any at all costs. There will be cases where using any is unavoidable but even that can be kept under control with an extra layer of abstraction.
Once you do that, TypeScript will speed up your development multifold because you no longer have to worry about and fiddle around with silly errors. It also makes a lot of unit tests redundant.
Once you start to use any in your project, it becomes a waste of time. You might as well drop TypeScript and go with plain JS.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I always recommend using TypeScript with strict mode on, while avoiding
anyat all costs. There will be cases where usinganyis unavoidable but even that can be kept under control with an extra layer of abstraction.Once you do that, TypeScript will speed up your development multifold because you no longer have to worry about and fiddle around with silly errors. It also makes a lot of unit tests redundant.
Once you start to use
anyin your project, it becomes a waste of time. You might as well drop TypeScript and go with plain JS.