This TypeScript story sounds familiar. Summary: 1. Adopt TypeScript. 2. Overuse "any". 3. Think TypeScript is useless. 4. Later realize...the problem wasn't TypeScript. It was overusing of "any".
The post is actually focused on React with lots of useful tips: freecodecamp.org/news/best-prac…
@housecor to be fair, a lot of the overuse of ‘any’ is because teams chose to migrate and then realized how much more time it takes to get the types right than they planned
@housecor Brings me back to 2018. Keep at it React devs
@housecor It’s the same with many tools and methodologies. Start writing tests, write a ton of unit tests, realize they’re making it hard for you to change the code, decide that tests are not worth it. Sadly, many never realize they wrote the wrong tests.
@housecor If there's a TypeScript error, I refuse to use any to fix it. Let it stay and be the constant reminder of my negligence 😅
@housecor Also problematic: interfaces with optional properties to enable them to be reused where separate interfaces would have been better
@housecor I can't understand why teams opt for TS then proceed to abuse any. Like it literally voids the entire point
@housecor Without a doubt "any" is a common problem to spot. I'm also worried about: 1. Defining types at the component level when they should be in a higher/reusable level 2. Changing the type because the dev is getting a TS warning, like making a type property optional