Member-only story
Why Typescript Won’t Save Your Project
If you have to choose between TypeScript and TDD, choose TDD.
Let’s be honest. The main reason you clicked on this to read is it has “Typescript” in the title. Love it or hate it, everyone is keen to learn more about Typescript. It seems like most people do one or the other. Love it or hate it, that is.
I am in the minority position that I pretty much do both. As a technician, I love the beauty of it, the fact that it presents me difficult and interesting problems to solve. That basically have no bearing on the problem domain. The entire purpose of those problems is to figure out how to explain to Typescript what I’m trying to do.
As someone who wants to deliver value to the business, I hate Typescript. I think in cases where Typescript does deliver value (which is not always), it probably does not deliver as much value as other things that could be done with the extra time it consumes.
Why Use TypeScript?
If you go to the Typescript website, they will tell you this about the problems TS is supposed to solve:
Typically, the need to ensure there are no bugs in your code can be handled by writing automated tests, then by manually verifying that the code works as you expect and finally having another person validate that it seems correct.
