|
Worse things can be seen:
int ONE_HUNDRED = 100;
ONE_HUNDRED++;
|
|
|
|
|
If it's any consolation, I've seen FORTRAN compilers which which will allow the equivalent of the following:
public void inc(ref int i)
{
i *= 2;
}
...
Console.WriteLine(100);
inc(100);
Console.WriteLine(100);
... And would print:
100
200 And I had to find that in production code...
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
|
|
|
|
|
LOOOOL!! This is me while reading your post:
Thanks for sharing such a pearl.
|
|
|
|
|
I have been a Contractor for 35 years. In that time I have been on about 40 or so projects most of which have been at least partial disasters. Some day I will write the whole gory details. I will make you belly laugh, then very very depressed.
|
|
|
|
|
<code>
public AssetInfo
{
....
public string CustAssID;
....
}
</code>
|
|
|
|
|
Well, errrr, some scientists say that each person's ass is unique, such as his/her fingerprint...
|
|
|
|
|
Imagine dusting for ass prints?
As an Atheist I am offended by any reference to religion.
I want all Muslims, Christians, Jews and [Insert fuller list of Religious Communities Here], to get the f*** off my planet and go live in space pixie land with the tooth fairy and the easter bunny. - DD
|
|
|
|
|
That might be the most appropriate ID name for a customer that I have ever seen.
I wasn't, now I am, then I won't be anymore.
|
|
|
|
|
They were only saving 2 characters with the abbreviation, so you know what was really on their mind.
|
|
|
|
|
awesome name
you just enlighten me ,take a look at this name
public TitlesInfo
{
....
// Customer Title id.
public string CustTitsID;
....
}
well, some scientist said there are no same tits in this world, too ,they are all unique .
Today is a gift, that's why we call it present
|
|
|
|
|
that can be called as 'programming with tits n ass of customer'
lol
|
|
|
|
|
Reminds me of my utility class for accessing assembly attributes:
public class AssInfo
{
... stuff ...
}
|
|
|
|
|
damn! thats nice. Why do you post it here and not in "clever code" ??
regards
Torsten
I never finish anyth...
|
|
|
|
|
We worked with a third party application designed in France - all the database table names were French abbreviations or acronyms. The "Authorized List" table was called ASS. Imagine the SQL when we desired to create a new record in that table:
"INSERT INTO ASS ..."
|
|
|
|
|
Really a way to show performance improvement.
Version 1.0
for ( int i = 0; i < data.Count; i++ )
{
Thread.Sleep(200);
container.Add(data[i].Items);
}
Version 2.0
for ( int i = 0; i < data.Count; i++ )
{
Thread.Sleep(100);
container.Add(data[i].Items);
}
Version 3.0
for ( int i = 0; i < data.Count; i++ )
{
container.Add(data[i].Items);
}
Should I tell the boss?
|
|
|
|
|
I would if I was you: he should have used a foreach ...
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
|
|
|
|
|
At this rate, you shouldn't expect the following code until about v43:
container.AddRange(data);
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
You will burn in hell!
|
|
|
|
|
Only tell the boss if the Version 1.0 and Version 2.0 devs are already gone from the company... Then you guys can have a good laugh about it.
BTW... I have seen something similar in code that I could trace back to one specific dev here where I work now. He is thankfully not with the company anymore.... He went to our biggest competition. YEAH!!!
I wasn't, now I am, then I won't be anymore.
|
|
|
|
|
Better hope Julian Assange doesn't get a hold of that leak.
|
|
|
|
|
Definitely. There's no excuse for
for ( int i = 0; i < data.Count; i++ )
instead of the obvious, clearly superior and faster
for ( int i = 0; i < data.Count; ++i )
|
|
|
|
|
Yes, it is surprising how few C++ programmers know that ++i executes faster than i++
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
CIDev wrote: Yes, it is surprising how few C++ programmers know that ++i executes faster than i++ Smile
Look at the assembly and you'll see why.
Fewer instructions to execute.
Gary
|
|
|
|
|
Because ++i doesn't have to keep track of/return the previous value of i.
|
|
|
|
|
The really sad thing is that most programmers don't know that i-- is the fastest way of the four...
I'd blame it on the Brain farts.. But let's be honest, it really is more like a Methane factory between my ears some days then it is anything else...
-----
"The conversations he was having with himself were becoming ominous."-.. On the radio...
|
|
|
|