|
I say he's not a programmer , he's a script kiddie. He can make a computer do something given enough time, but has no place in professional code.
If it moves, compile it
|
|
|
|
|
Think I got as far as & vbCrLf before I knew it was going to be some fun.
Thanks! It certainly didn't disappoint.
|
|
|
|
|
loctrice wrote: I don't know what to say
I second that. Well... I know what to say, but there's too much and 99.999% of it is not really kid sister safe to say 
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
|
Wow, that is some of the worst garbage code I have seen and I have seen a lot of poor code. 
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
Trust me , this is nothing compared to his regular coding. Just a little window from what is, for him, a clean file. I just had enough of dealing with it this time and decided to post.
If it moves, compile it
|
|
|
|
|
My sympathies to you for having to put up with that nonsense.
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
This guy must be brilliant if he can write that much code! 
What's best about code such as this is it is really easy to maintain. Need to store anything? Just use Rtn! Need a new variable? Name it Rtn! Need input? Rtn! Need output? Rtn!
Rtn, your all-round coding solution, now coming to code near you!
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}
|
|
|
|
|
Found this in my colleagues' code today. We had a good laugh on that 
\\ some code
var item = values.TryGet<ITimelineItem>(3);
var dt = (DateTime)values[0];
var tomorrow = new DateTime(2012, 4, 26);
if(item != null)
\\ some more code
|
|
|
|
|
Christian Brüggemann wrote: my colleague
You surely mean ex-colleague. By rough estimations, he should have been shot a few times
|
|
|
|
|
|
var tomorrow = new DateTime(2012, 4, 26);
Fixed the comment for you
|
|
|
|
|
Just one error I see in there...
var twentySixthAprilTwoThousandAndTwelve = new DateTime(2012, 4, 26); FTFY
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}
|
|
|
|
|
When I see stuff like this I genuinely don't know whether to laugh or cry! 
|
|
|
|
|
Here's one person that believes coding languages do evolve.
|
|
|
|
|
You won't believe it but I found very similar line in our code a few days ago, just the variable name was "yesterday" and it was set to May 22.
|
|
|
|
|
Humm, must be a new pattern. 
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
Or the same employee, different company.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
----
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
|
But, hey, it worked without errors when he wrote and debugged it on April 25th. Actually it looks like it might have been used to trigger some event on the 25th - but for only 2012? Scratch that! Why code to look for tomorrow instead of today.
I'm through trying to rationalize this. I guess I try to assume there is a reason for everything and people are better then they really are. 
Hope it wasn't moved into production.
|
|
|
|
|
Simple rationale - running this on a test system and the last day that the test system has data for is 4/26. A quick change to the code for debug purposes, just make sure to roll it back before release... oops!
|
|
|
|
|
#if DEBUG
#else
#endif anyone?
public class SysAdmin : Employee
{
public override void DoWork(IWorkItem workItem)
{
if (workItem.User.Type == UserType.NoLearn){
throw new NoIWillNotFixYourComputerException(new Luser(workItem.User));
}else{
base.DoWork(workItem);
}
}
}
|
|
|
|
|
Zac Greve wrote: #if DEBUG
#else
#endif
True, and I do that a lot. Though it's bit me a couple times that I now watch out for...
a) In most situations I'd really rather have 3 levels - DEBUG on my dev machine, DEBUG on the dev server, RELEASE on the production server.
b) Release code paths don't get tested as thoroughly until uploaded to the production server. I mean - you have to test them, but if you wrap everything in #if DEBUG directives, it can be nontrivial to run in VS on a dev system in RELEASE mode.
|
|
|
|
|
Looks like someone found a way to stop time.
|
|
|
|
|
Should it have been:
var tomorrow = new DateTime(2012, 2, 3);
var today = "Groundhog Day";
|
|
|
|
|
if (wttResultsDataTable.Rows.Count == 1000)
{
if (wttResultsDataTable != null)
{
if (wttResultsDataTable.Rows.Count > 0 && DCTReportRoot.errorFlagRaised == false)
{
Besides the fact, the code would blow up before this point if wttResultsDataTable was null, wouldn't the first if blow up if it was null?
|
|
|
|
|
Nice piece of work, if wttResultsDataTable is really null application will fail in the first place 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
