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.
In [Machine SUIF](http://www.eecs.harvard.edu/hube/software/nci/overview.html), Mike Smith and Glenn Holloway *rigidly* enforce the case convention that a capital letter marks a new word. So even though CPS is an acronym it's `transformToCps` and not `transformToCPS`. I have found that in the long run, their method works better than what we did in [Quick C--](http://www.cminusminus.org), where we usually did all caps for cases like ID and CPS.