I like to give descriptive names for my variables, methods, and objects. Obviously, he does not go overboard, but let me give you a few examples.
public class Account
{
public decimal Balance { get; set; }
}
Account account = new Account();
account.Balance = 1000;
Some people will want to do the following, which really does not make sense to me if you are not a lazy typist.
Account acc = new Account();
acc.Balance = 1000;
The problem is that you have logic with these abbreviations. You are very confused about what is happening.
Imagine the following objects.
public class Account { public DebitOrder DebitOrder { get; set; } }
public class DebitOrder { BankDetail BankDetail { get; set; } }
public class BankDetail {}
Account acc = new Account();
DebitOrder do = new DebitOrder();
BankDetail bd = new BankDetail();
if(acc.DebitOrder.SomeProperty == do.SomeProperty)
{
}
Readability is declining. There is always an intellisense argument and just hangs over your variables to see what type they are, or what they are. Readable code makes code easy to understand.
Are naming conventions consistent with improved supported code?