1) It's unmaintainable.
2) It's ugly.
If you ever need a semantic naming convention for closely related variables that are crucial to use correctly (encryptedCustomerInformation vs decryptedCustomerInformation), make up your own ad hoc.
2) It's ugly.
If you ever need a semantic naming convention for closely related variables that are crucial to use correctly (encryptedCustomerInformation vs decryptedCustomerInformation), make up your own ad hoc.
It may be trouble to determine what the prefixes mean. To have no pattern at all, IMO is not at all an improvement.
Why is that? The only time I've ever seen 'Hungarian' notation cause maintenance problems is when a dev changed the type of a variable without adjusting the name accordingly. That's a problem with the developer, not the convention.
It's ugly.
That's purely subjective.