[{"slug":"my-typescript-workflow","frontmatter":{"content":"\nTypeScript can slow the development down if not used properly. You may ask how? It can do it by making you think about the compilation errors when you have just started coding a project.\n\nWhile building something the most important thing is quickly applying the ideas that you have in your mind to see a working prototype. If you go and start fixing those compilation errors it's a huge mental burden and it takes you in a different direction where you are just fixing those errors.\n\n**How I use TypeScript to push me faster in the right direction**\n\n- Don't use TypeScript everywhere. If you feel it is a decently complex codebase, then use it.\n - Remember that with TypeScript's `checkJs` and `allowJs` options, JS files can have Type Safety using [JSDoc](https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html) which can be added on a need basis.\n- I use TypeScript in strict mode. I want it to be the harshest critique of my code.\n- I think of TypeScript as automation tests with a super bonus of IDE auto-completion and documentation generation.\n- If a test is failing while I am building something, I would like to be aware of it but not immediately work on fixing it. The same is with TypeScript.\n- It doesn't mean that I would only fix those TypeScript compilation errors only after the entire project is done. NO. It defeats the purpose of using TypeScript.\n- Identify small milestones and then fix those compilation errors. e.g. a function(say *addComment*) has been written and its implementation is done. At this moment, I would make it fully TypeScript compliant, so that whenever I have to make a change in it in future(very near, near or far), my TypeScript tests are there to save me.","data":{"category":"TypeScript, productivity","creationTs":1630726500000,"date":"September 4, 2021 5:35 AM","lastModified":"September 9, 2021 3:10 PM","lastModifiedTs":1631193000000,"published":"Yes","title":"My TypeScript workflow"},"isEmpty":false,"excerpt":"","category":["TypeScript","productivity"],"creationTs":1630726500000,"date":"September 4, 2021","lastModified":"September 9, 2021 3:10 PM","lastModifiedTs":1631193000000,"published":"Yes","title":"My TypeScript workflow","updated":"September 9, 2021"},"content":"

TypeScript can slow the development down if not used properly. You may ask how? It can do it by making you think about the compilation errors when you have just started coding a project.

While building something the most important thing is quickly applying the ideas that you have in your mind to see a working prototype. If you go and start fixing those compilation errors it's a huge mental burden and it takes you in a different direction where you are just fixing those errors.

How I use TypeScript to push me faster in the right direction

Don't use TypeScript everywhere. If you feel it is a decently complex codebase, then use it.
- Remember that with TypeScript's checkJs and allowJs options, JS files can have Type Safety using JSDoc which can be added on a need basis.
\n
I use TypeScript in strict mode. I want it to be the harshest critique of my code.
I think of TypeScript as automation tests with a super bonus of IDE auto-completion and documentation generation.
If a test is failing while I am building something, I would like to be aware of it but not immediately work on fixing it. The same is with TypeScript.
It doesn't mean that I would only fix those TypeScript compilation errors only after the entire project is done. NO. It defeats the purpose of using TypeScript.
Identify small milestones and then fix those compilation errors. e.g. a function(say addComment) has been written and its implementation is done. At this moment, I would make it fully TypeScript compliant, so that whenever I have to make a change in it in future(very near, near or far), my TypeScript tests are there to save me.

\n"}]

Category: TypeScript