Here is one I could never find a good solution for:

Parameter names (i.e. variable names that you pass to the function) in a modifier.  For example:

class DoesNothing {
public:
  DoesNothing();
  void Weight(int ???);
private:
  int weight;
};

I am opposed most of the time to call things "myWeight" for the class variables.  paramWeight seems to be too lengthy for the "???".

As I look at Ricky's example, it looks like you two are talking about either C++ or Java with the { 's.   I am not sure what naming conventions you should use, MathsIsFun, in regard to either of those languages. I am teaching myself some Java, and I like it so far.

That's right, I am not being specific as to language (but we should be aware that many languages are case sensitive).

Ricky wrote:

I am opposed most of the time to call things "myWeight" for the class variables.  paramWeight seems to be too lengthy for the "???".

I have used newWeight and also TheWeight in cases like that ... it is somewhat annoying I agree.

Chewy wrote:

dim intBeans
dim intPots   etc...

I personally do not like putting the type in the name (like intBeans or charID) because if you need to change the type you then have to do variable renaming, and possibly miss one.

my lecturer always says give it a name that means something because it will be easier to understand when reading over, in functions the first letter in the word should be in lower case but after that to have them startin with an upper case letter e.g getLengthOfArray(). he also believes that member data should start with m_ eg m_Data

It is ugly. I wouldn't use m_Data,  a week later I wouldn't remember what it meant. Unless my proggie is heavily commented, I have no chance of understanding it later.