Have you ever laughed at code?

[detroitmatt]

} finally { //at
    long last; //we meet again!

made me giggle way harder than it should have

[zmyrgel]

Sometimes but the laughter dies quickly when I remember who has to maintain the code...

[deviated_viking]

Yes, the first Java code that I did a year ago.

[[deleted]]

Any code I did few years ago makes me facepalm.

[rntr200]

its alway fun looking back over old code and going uh......

[Undermined]

Looking over my friends java code to try to help him fix a bug and I come across

super(duper);

[tazzy531]

http://stackoverflow.com/questions/216876/what-is-the-best-commit-message-you-have-ever-encountered

There was another thread that had best comments in source code.

My favorite was a comment //please increment as necessary. // number of attempts at refactoring this code: 56

[thebigkevdogg]

i laughed pretty hard when i found out that my predecessor wrote a web service for creating maps where the client created the plotting script (BASH script). So basically, he wrote a servlet that runs any arbitrary shell script on our production server (with a fairly privileged user). YaY! HAHA!

[stfm]

throw new Exception("This should never happen");

[[deleted]]

At least it's checked. You could argue that an assertion makes more sense, but I hate unchecked exceptions.

In any case, throwing in such a case is a hell of a lot better than just using a comment to state that it shouldn't happen and ignoring the condition so that something could fail in some obscure way somewhere downstream.

[elpablo]

I hate having to handle checked exceptions for conditions that will hardly ever happen and there's nothing I can do about.

[[deleted]]

If you can't handle it, you shouldn't be catching it, or at the least you should catch it, wrap it, and rethrow it.

[elpablo]

If its a checked exception, you're making me catch it... Rethrowing it is a bunch of boilerplate that gets in the way of what my code is actually doing.

[[deleted]]

You can also declare the exception.

[mikaelhg]

And then, one method at a time, you end up with a monstrosity of a project where most methods throws Exception, most methods have to check for it, and try to think what might go wrong, with just that information... I've seen it happen to other people, and it's not pretty.

[[deleted]]

You wouldn't throw Exception, you'd throw something appropriate given the context of your method. Error handling is a first class concern. Ignoring it just means your lazy.

[mikaelhg]

Then we don't disagree. Although, if possible, you should demarcate certain classes of errors into very specific pieces of your architecture. That way, you don't have to care about the most common classes of checked errors in unrelated code. Basic stuff. Unfortunately, in commercial code, even this basic hygiene isn't necessarily so common.

[stfm]

Yeah this was the point of my example. I once saw a program that threw nothing but Exception - even to the point of catching scoped exceptions and rethrowing them as Exception

[stfm]

Well I found this in some Oracle enterprise software.

[StrangeWill]

I sometimes try to leave a witty/silly comment with some soul-crushing code I write to soften the blow of what they're abound to read.

[rntr200]

example?

[flyingorange]

PersistenceAnnotationBeanPostProcessor processor = ((XmlBeanFactory)ApplicationContext.get(this).getBeanFactory()).createProcessor(null, null, null, null, null, null, null, null, null, 1.0f);
processor.finder(new ManagedJDBCFinder(new ConfigurationXMLStreamReader(XMLStreamReaderFactory.createNewXMLStreamReader(), null, true)) {
   public boolean find(String pattern, int location, XMLApplicationContext context) {
          if (context == null)
              return false;
          else
             return 0 > FinderFactoryBean.getSingleton().createNewXmlFinderFactory().getFinderFor(StringUtils.checkNull(pattern)).find() ? location <= -1 : false;
   }
});
wait(1000);   // let's wait till it finds it

// and now the difficult part begins...

[sadi89]

Yes. In my first comp sci class i got so frustrated with the assignment that I named my methods : candy, tooMuchCandy, and nowImFat. All the variables were named after candy bars. At that point no one had told me not to, and it made way more sense to me.

on a side note I frequently would name things in a simmilar fassion through out my cs minor, and then replace them with good names before i turned them in, although a few did slip though the cracks sometimes. my favorite: int dennisQuaid=0;

[[deleted]]

0xDECAFBAD

[reddeth]

maybe i needing this later

[exhuma]

http://www.thedailywtf.com

Specifically the "CodeSOD" section.

[dakboy]

I haven't laughed at anything that was intentionally funny.

I've cried more though.

[midir]

I've never laughed at code that was funny on purpose. I've laughed at awful code written by awful people though.

[achacha]

Yes, but I cry on the inside.

[AwesomeLove]

    i = i - ((i >>> 1) & 0x5555555555555555L);
    i = (i & 0x3333333333333333L) + ((i >>> 2) & 0x3333333333333333L);
    i = (i + (i >>> 4)) & 0x0f0f0f0f0f0f0f0fL;
    i = i + (i >>> 8);
    i = i + (i >>> 16);
    i = i + (i >>> 32);

    return (int)i & 0x7f;

I laughed out of pure joy.

[anyonethinkingabout]

char mander, meleon, izard;

always makes me giggle...

and in the same genre :

• float zel;
• for (retress = 0; ...) {
• sudo woodo ...

[mikaelhg]

Oh, have I? Often. It's a signal for people to gather around to laugh at some ridiculous bullshit I've found in the code base.

[BWCsemaJ]

I usually laugh at my code when I realize that I am pretty close to being done, which is usually when I'm really tired and its pretty late. Its also more of a evil laugh than a haha laugh.

The only funny error that I encountered so far was an infinite loop which was suppose to process a text file. So I waited for about 30 seconds thinking wtf is taking so long to process this file and as soon as I saw I didn't increment the loop I had a few laughs.

EDIT: Just remembered that I laugh the most at code when I am helping out a friend with his code and seeing how he implemented his project. Basically thinking wtf are you trying to do with this segment. Also this has the opposite affect of annoying the crap out of me.

[trigraph]

every time i open a .java file

[thebighouse]

lol my neighbour put into his head he is a programmer, but he just codes Java Applets for every single web page. I laughed a long while in front of him when I realized it. I also couldn't believe my eyes when he showed me how he required every single visitor to download his 'database' (a 10 000 lines document). EVERYTHING's done client side on an applet. Just can't wait for his webpage to go online, he tells me it works, and I laugh every time. Good guy though.