Overall a questionable list of unproven claims. E.g.:
> Hype: "Static Typing reduces bugs."
Just because the author has not found proper research proving it doesn't mean it's false.
A great type system with sum types prevents tons of bugs. I wonder how anyone can question this.
> Hype: "Identifiers should be self-documenting! Use full names, not abbreviations."
Same as above. To fix bugs you need to read and understand the code. Not having to map abbreviations to your mental model reduces overhead. I've seen code bases where u was used as an abbreviation for user and users in different methods. That was not a fun code base.
Some developers and teams don't need the crutches. Type systems are also an encumbrance that comes with a non zero amount of issues. They slow development velocity down for a theoretical trade-off boon.
I've seen a type system take down a production system where a simple coercion would have functioned just fine. Literally the only thing wrong was the type defined and the code refused to run.
> Hype: "Static Typing reduces bugs."
Just because the author has not found proper research proving it doesn't mean it's false.
A great type system with sum types prevents tons of bugs. I wonder how anyone can question this.
> Hype: "Identifiers should be self-documenting! Use full names, not abbreviations."
Same as above. To fix bugs you need to read and understand the code. Not having to map abbreviations to your mental model reduces overhead. I've seen code bases where u was used as an abbreviation for user and users in different methods. That was not a fun code base.