Of names and naming conventions…

I wish that developers would realize that some naming conventions are no longer necessary. At my present job, we have a developer who insists on putting an E before the name of an enumerated type. Like ColumnType becomes EColumnType. His claim is that it helps readability, and you know it’s an enumerated type without looking at the definition. I’ve tried to point out that the compiler will gladly point out when you’re using an enumerated type incorrectly, and won’t let you use it where it’s not appropriate (this is C# mind you). 

Alas, he still does it. I know he does it because C allows you to use integers where an enumerated value can be and vice-versa, but still, it’s 2008, C# and other modern languages have changed to help prevent you from doing stupid things (unless you really mean to). Just let the compiler do it’s job.