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 do what I feel like. In general, your best practice is to err in favor of readability vs. compliance with some abstract standard. 

Just be consistent.
It's pronounced "eye dee", not "id as in id, ego and superego", so ID, not Id. That's my vote, anyhow. The fact that it's an abbreviation, rather than an acronym is irrelevant, due to the way that it's pronounced. It's pronounced as if it were an acronym, so it may as well be typed that way as well. Oh, and camel case is the worst idea in the history of computing.:)