Why name things sensibly, when you could also not?
-
The application I'm newly tasked with maintaining is a large heap of WTF, but I picked this problem out to share because it demonstrates the supreme barrier to understanding that the prior developer(s) have constructed:
#define __2__
// snip
#if __2__
// some comment-less code that has nothing ostensibly to do with the number 2
#else
// some other comment-less code that appears to have no relationship at all
// to the prior alternative
#endif:doh: :omg: :wtf: Actually, there are many comments all over the code, but of the sort that tell you absolutely nothing:
//only check if max > -1
if (max > -1)
{
...
}Why name that variable maxCsvPosition when a careful analysis of the dozens of lines of surrounding code will tell you that? What are you, lazy? And even dozens of lines is often a luxury—many of the methods in this thing are many hundreds of lines long! The variable names are typically like the following, their scope often spanning many screens' worth of code:
ed1
s
sd
p
pdShouting curse words with great frequency has become my new affect here at t'office. I despair :((
-
The application I'm newly tasked with maintaining is a large heap of WTF, but I picked this problem out to share because it demonstrates the supreme barrier to understanding that the prior developer(s) have constructed:
#define __2__
// snip
#if __2__
// some comment-less code that has nothing ostensibly to do with the number 2
#else
// some other comment-less code that appears to have no relationship at all
// to the prior alternative
#endif:doh: :omg: :wtf: Actually, there are many comments all over the code, but of the sort that tell you absolutely nothing:
//only check if max > -1
if (max > -1)
{
...
}Why name that variable maxCsvPosition when a careful analysis of the dozens of lines of surrounding code will tell you that? What are you, lazy? And even dozens of lines is often a luxury—many of the methods in this thing are many hundreds of lines long! The variable names are typically like the following, their scope often spanning many screens' worth of code:
ed1
s
sd
p
pdShouting curse words with great frequency has become my new affect here at t'office. I despair :((
Variable naming rule 0) You don't have to name the variables you don't create.
-
The application I'm newly tasked with maintaining is a large heap of WTF, but I picked this problem out to share because it demonstrates the supreme barrier to understanding that the prior developer(s) have constructed:
#define __2__
// snip
#if __2__
// some comment-less code that has nothing ostensibly to do with the number 2
#else
// some other comment-less code that appears to have no relationship at all
// to the prior alternative
#endif:doh: :omg: :wtf: Actually, there are many comments all over the code, but of the sort that tell you absolutely nothing:
//only check if max > -1
if (max > -1)
{
...
}Why name that variable maxCsvPosition when a careful analysis of the dozens of lines of surrounding code will tell you that? What are you, lazy? And even dozens of lines is often a luxury—many of the methods in this thing are many hundreds of lines long! The variable names are typically like the following, their scope often spanning many screens' worth of code:
ed1
s
sd
p
pdShouting curse words with great frequency has become my new affect here at t'office. I despair :((
My deciphering of four of those variable names is:
s // represents 'something'
sd // something different
p // pointer to s
pd // pointer to sd:-)
-
The application I'm newly tasked with maintaining is a large heap of WTF, but I picked this problem out to share because it demonstrates the supreme barrier to understanding that the prior developer(s) have constructed:
#define __2__
// snip
#if __2__
// some comment-less code that has nothing ostensibly to do with the number 2
#else
// some other comment-less code that appears to have no relationship at all
// to the prior alternative
#endif:doh: :omg: :wtf: Actually, there are many comments all over the code, but of the sort that tell you absolutely nothing:
//only check if max > -1
if (max > -1)
{
...
}Why name that variable maxCsvPosition when a careful analysis of the dozens of lines of surrounding code will tell you that? What are you, lazy? And even dozens of lines is often a luxury—many of the methods in this thing are many hundreds of lines long! The variable names are typically like the following, their scope often spanning many screens' worth of code:
ed1
s
sd
p
pdShouting curse words with great frequency has become my new affect here at t'office. I despair :((
This inspired me a little haiku! ;P
if (nameOfUser)
name ++;
for (var word = 0; word < name; lowercase(ref word)) {
Comments(ref products);
}All in one Menu-Ribbon Bar DirectX for WinRT/C# since 2013! Taking over the world since 1371!
-
My deciphering of four of those variable names is:
s // represents 'something'
sd // something different
p // pointer to s
pd // pointer to sd:-)
-
The application I'm newly tasked with maintaining is a large heap of WTF, but I picked this problem out to share because it demonstrates the supreme barrier to understanding that the prior developer(s) have constructed:
#define __2__
// snip
#if __2__
// some comment-less code that has nothing ostensibly to do with the number 2
#else
// some other comment-less code that appears to have no relationship at all
// to the prior alternative
#endif:doh: :omg: :wtf: Actually, there are many comments all over the code, but of the sort that tell you absolutely nothing:
//only check if max > -1
if (max > -1)
{
...
}Why name that variable maxCsvPosition when a careful analysis of the dozens of lines of surrounding code will tell you that? What are you, lazy? And even dozens of lines is often a luxury—many of the methods in this thing are many hundreds of lines long! The variable names are typically like the following, their scope often spanning many screens' worth of code:
ed1
s
sd
p
pdShouting curse words with great frequency has become my new affect here at t'office. I despair :((
Well, with number two ... why not flush down the sh1t?
-
The application I'm newly tasked with maintaining is a large heap of WTF, but I picked this problem out to share because it demonstrates the supreme barrier to understanding that the prior developer(s) have constructed:
#define __2__
// snip
#if __2__
// some comment-less code that has nothing ostensibly to do with the number 2
#else
// some other comment-less code that appears to have no relationship at all
// to the prior alternative
#endif:doh: :omg: :wtf: Actually, there are many comments all over the code, but of the sort that tell you absolutely nothing:
//only check if max > -1
if (max > -1)
{
...
}Why name that variable maxCsvPosition when a careful analysis of the dozens of lines of surrounding code will tell you that? What are you, lazy? And even dozens of lines is often a luxury—many of the methods in this thing are many hundreds of lines long! The variable names are typically like the following, their scope often spanning many screens' worth of code:
ed1
s
sd
p
pdShouting curse words with great frequency has become my new affect here at t'office. I despair :((
WTF? Whoever wrote that code needs to have a frontal lobotomy... As they are obviously antisocial psychopaths!
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
The application I'm newly tasked with maintaining is a large heap of WTF, but I picked this problem out to share because it demonstrates the supreme barrier to understanding that the prior developer(s) have constructed:
#define __2__
// snip
#if __2__
// some comment-less code that has nothing ostensibly to do with the number 2
#else
// some other comment-less code that appears to have no relationship at all
// to the prior alternative
#endif:doh: :omg: :wtf: Actually, there are many comments all over the code, but of the sort that tell you absolutely nothing:
//only check if max > -1
if (max > -1)
{
...
}Why name that variable maxCsvPosition when a careful analysis of the dozens of lines of surrounding code will tell you that? What are you, lazy? And even dozens of lines is often a luxury—many of the methods in this thing are many hundreds of lines long! The variable names are typically like the following, their scope often spanning many screens' worth of code:
ed1
s
sd
p
pdShouting curse words with great frequency has become my new affect here at t'office. I despair :((
-
The application I'm newly tasked with maintaining is a large heap of WTF, but I picked this problem out to share because it demonstrates the supreme barrier to understanding that the prior developer(s) have constructed:
#define __2__
// snip
#if __2__
// some comment-less code that has nothing ostensibly to do with the number 2
#else
// some other comment-less code that appears to have no relationship at all
// to the prior alternative
#endif:doh: :omg: :wtf: Actually, there are many comments all over the code, but of the sort that tell you absolutely nothing:
//only check if max > -1
if (max > -1)
{
...
}Why name that variable maxCsvPosition when a careful analysis of the dozens of lines of surrounding code will tell you that? What are you, lazy? And even dozens of lines is often a luxury—many of the methods in this thing are many hundreds of lines long! The variable names are typically like the following, their scope often spanning many screens' worth of code:
ed1
s
sd
p
pdShouting curse words with great frequency has become my new affect here at t'office. I despair :((
Maybe someone else wrote perfectly sensible application with full names and such...and deployed it obfuscated...finally, someone (obviously not the same someone :-\ ) reflected it back to code and sold it as his own :)
-
WTF? Whoever wrote that code needs to have a frontal lobotomy... As they are obviously antisocial psychopaths!
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
Given that they wrote the code to begin with, I think the lobotomy is already accomplished.
Software Zen:
delete this; -
WTF? Whoever wrote that code needs to have a frontal lobotomy... As they are obviously antisocial psychopaths!
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???