This is in some respects statistics rather than programming, but it is related. I am slowly writing a program that is going to be entered in a competition and as usual it isn't the programming that is causing the problem, but the theory behind it.
I have a set of data which contains multiple variables on how well the user preformed at answering a question, where each question has a set of tags. I need to, when given a set of tags, predict how well the user is going to do at answering the question.
I am assuming that someone has done some work or written a paper on it somewhere, but I have not managed to find anything. Does anyone know of any research or information relating to the problem? I may have just been googling for the wrong terms.
Other names.. Private class member variables I usually start with a prefix "m_", function parameters with just an underscore "_", local variables without one. Variables in general are prefixed with the type. "l" for long, "s" for strings etc. Arrays are prefixed with an "a". It makes the code quicker and easier to read for me. This way I can also tell where to look for the declaration even if I was out of the IDE looking at a diff report on the changes someone else made to the file. Why is this a bad thing? Maybe it's just an old habit because I've used a similar naming convention for many years.
The only thing I do is start class variables with an m, mainly because in C++ you don't require 'this->'. (Just 'm' as can't stand underscores as they are I don't like typing them.). I have never had an issue with knowing what type a variable is as I can (most of the time) manage to infer it from the variable name. This is probably because I only really either read my own code or very well written code (Ogre3D etc). Given the "professional" code I have worked with, I expect that will change.