>tfw you spend half your time thinking of good variable and

yeah stop being autistic

> get-verb
select the verb that matches the functions use
> describe the function in as little words as possible

example: for a function that returns an ip address "get-ipaddress", for a function that returns a bool if an ip address exists "test-ifup"

>name test variables nigger
>sometimes forget to delete them after commenting them out

>>61652002
name variables after porn stars you like whacking it to.

>>61652002
I think Apple has a style guide on this, if you really, really like typing.

>>61652152
I only watch amateur stuff.

>>61652121
For what purpose?

File: 1335124477361.jpg (37KB, 627x474px) Image search: [Google]

37KB, 627x474px

>>61652101
>powershell

>>61652121
This
Something I do something similar printing during debugging.
Usually I use stupid short names like "l_c" or "kk" because I'm lazy and fuck readability.

date +%s%3N

>>61652002
x
xx
xxx
xxxx
xxxxx
xxxxxx

dumb catposter

It doesn't necessarily matter what the function name is if you docblock it well, and for variables I don't understand your problem. Just name them after the information they represent in less than 3 words.

>>61652121
I do this
Cept its not just test variables, i just never publish my code (actually pretty much the reason I don't either)
Although sometimes they're more like actual names and it ends up looking like

while(!isGay) 
    doStufff(ass);

>>61653446
This seems like a pretty good approach actually. I did something similar a few years back while working on a new averaging function.

>>61652002
Just do what I do and name them after races/ethnicities that you despise.
Nigger
Kike
Spic
Chink
And so on.

>>61652257
>posting derelle
heh