type-challenges VS tooling.report

View on GitHub

For those who want to improve their type level skills, I highly recommend this repository for learning by doing: https://github.com/type-challenges/type-challenges.

I'm very like typescript and I always try to learn something interesting there. I thought that it is impossible to know the length of the string in typescript, but I was wrong. Today during solving typescript challenge I found a way to do it. If you don't know about typescript challenges, you can read about it here, it is a very interesting project, and I highly recommend you to try it, if you, like me, obsessed with typescript.

For those wonder why you don’t need a CS degree, I invite you to solve the type problems here https://github.com/type-challenges/type-challenges. No degree needed and if you can solve those problems with ease (as really understand the problems), you can work on any problems in any business.

It's not really a major usage but I think it would be cool to see if a coding model could be fine-tuned to take in a prompt of instructions and output a valid Typescript type solution (like in https://github.com/type-challenges/type-challenges)

This article is more an overview than a feature comparison. The Tooling Report is your best guide to understand of the features supported by some of the tools mentioned here.

GoogleChromeLabs/tooling.report