• Create Account

### #ActualBacterius

Posted 14 April 2013 - 11:29 PM

I also imagine that for those with a heavy maths background they will try to name program variables as if they were doing so in an equation out of custom (since in equations everything is a letter and maybe a subscript).

True, but in general equation variables are named sensibly. I have trouble conceiving an equation mapping to this:

step_int((-ima*bxz-qjdiv*bxy)*xsp)


Nah it just looks like someone trying to use 1-letter variables, running out, moving on to 2-letter variables, running out, and so on.

Reasonable variable names are descriptive stuff like "delta", "x_prime", "du", and so on. But having multiple variables called "disx", "disy", "disxl", "disxr", "disx2", "disxr2" is unreasonable. It's insane. You have to look up their meaning to invoke them when needed, unless you know the code by heart (which should not be the case for even remotely self-documenting code). It might be good for a code-and-forget kind of project or library, but good luck maintaining this.

PS: or excessive precomputation, maybe.

### #1Bacterius

Posted 14 April 2013 - 11:24 PM

I also imagine that for those with a heavy maths background they will try to name program variables as if they were doing so in an equation out of custom (since in equations everything is a letter and maybe a subscript).

True, but in general equation variables are named sensibly. I have trouble conceiving an equation mapping to this:

step_int((-ima*bxz-qjdiv*bxy)*xsp)


Nah it just looks like someone trying to use 1-letter variables, running out, moving on to 2-letter variables, running out, and so on.

PARTNERS