really started to show.
completely optional) but the most important thing it adds is a compile step where it does a static analysis of your code to make sure everything looks basically correct.
team, Joe, needs me to change the way a set of functions I wrote work. These changes require me to have to change the parameters passed to that function. I make the changes and Joe's happy. The problem is you use the functions too and
need to do is compile and it's going to give me a build break for anywhere I need to change. With TypeScript I simply need to keep fixing breaks until the project compiles and I can then be pretty certain that I've update all places that reference the
code I changed. The more complex the change the more TypeScripts compile step is going to help you.
That was a refactoring example but even when you're writing new code there's a benefit with using TypeScript... typeo's... ever misspelled a function name? with TYpeScript that's not going to happen because the compilers going to catch your typo.