Question: I use `camelCase` in my code and database field names, etc, but with fields that have `Id` at the end, it always ends up being hard to read. For example, `itemId`, `teacherId`, `unitId`, etc. In these cases I consider breaking convention and writing `itemID, teacherID, or unitID` just for improved readability.

What do you do and what's a general, best practice of dealing with this issue?

Answer: 
I actually prefer "ID". But, as everyone says, consistency is the most important thing.

Steve
I think that readability is of utmost importance, and should override your convention if it's going to make it that much easier to read. I think the cons outweigh the pros for sticking to your guns/convention if you can't read it easily (as much as we programmers hate to break conventions and protocols).