Original sentence: Furthermore, if you don't know what a variable is used for, knowing its type won't help you.If a variable's type is changed, either the decoration on the name of the variable will be inconsistent with the new type, or the variable's name must be changed.Some modern Integrated development environments, such as Visual Basic display variable types on demand, and automatically flag operations which use incompatible types, making the notation largely obsolete
Edited sentence: Furthermore, if you don't know what a variable is used for, knowing its type won't help you - which is an issue with the skill of the user which does not, in and of itself, debunk the use of the notation.If a variable's type is changed, either the decoration on the name of the variable will be inconsistent with the new type, or the variable's name must be changed - though this is more the lack of rigor applied by the maintainer and an issue for quality control.In the end it is a vehicle for standardising code, much like any and all attempts at a coding standard (or facet thereof) and is used and misused in equal parts.Some modern Integrated development environments, such as Visual Basic display variable types on demand, and automatically flag operations which use incompatible types, making the notation, like Visual Basic, largely obsolete.The problem with this criticism is, of course, the notation is to aid program understanding, what is often "implicit" to the developer is lost on the reader because the developer has tacit knowledge of the software