9. Be As Strict As Possible
Strict TypeScript and ESLint feel restrictive at first, but they catch bugs before they ever reach your code — and that saves time in the long run.
🛡️ One of the best ways to prevent errors in an application is to work as strictly as possible. Strict code helps you avoid issues with your data and application behavior before they even occur. This means building in as many checks as possible to validate both your application and the data it handles.
🔧 Personally, I like to use TypeScript with the strictest possible configuration, combined with an extensive and very strict ESLint setup. This enforces strict coding practices within a project. For some developers, this can be a bit challenging at first — "Why am I suddenly not allowed to do so many things?" — and it might feel like development takes more time. However, they usually realize fairly quickly that it actually saves them time in the long run, because the application becomes much more stable. Bugs that never make it into your code don't need fixing later.
💡 That's why this week's tile is: "Be As Strict As Possible."
What many developers don't know is that in TypeScript, you can create highly advanced types that make your code even stricter and more robust. In the coming weeks, I'll be sharing some of these tricks with you in separate articles.
💬 So what do you think? Should code be as strict as possible? And what do you do to keep your codebase as solid as you can?
🚀 Could your project use a bit more strictness? Feel free to reach out — I'd be happy to help.
📌 This article is part of my series "Developers Tiles of Wisdom." Follow me for more wisdom tiles!
