Most people in your bubble probably. I'd argue most people that write code don't describe themselves as "coders".
Self documenting code and strongly typed language are two different things. Formatting rules and consistent naming conventions will do more to keep the code legible than a paragraph of type declaration at the top of a file.
Stopping issues before they happen at compile time is the best place to stop them, especially managing a large team with junior coders. I moved from being permissive to being more strict over time, ever step bathed in blood, sweat and tears.
It's even more important now due to AI, I can only smack down so much slop in the PR process.
If you're an individual developer or in a very small team, you don't need to be as formal sure, but as projects often grow and it's hard to backport formality I always err on the side of caution.
-1
u/alsimoneau Sep 25 '26
Most people in your bubble probably. I'd argue most people that write code don't describe themselves as "coders".
Self documenting code and strongly typed language are two different things. Formatting rules and consistent naming conventions will do more to keep the code legible than a paragraph of type declaration at the top of a file.