Live data from Hacker News

The worst program I ever worked on

jacquesmattheij.com

31–40 of 136 posts

Re: The worst program I ever worked on

#31

The only place where the names made any immediate sense was 'main' and any C stdlib calls. Any job worth doing is worth doing right. Contrariwise, any job worth fucking up is worth fucking up stupendously. He didn't go all the way. #define monkeymeat printf #define turtlescrotum malloc #define wolfnipplechips gets #define chipotlaway exit ...

    #define HEREWEGO {
    #define ENOUGHNOW }

Re: The worst program I ever worked on

#32
post #20

This is off topic but I find it difficult to read the blog-articles from jaquesmattheij.com . Zooming doesn't help because the text doesn't wrap correctly. Just a suggestion for the author to change the layout of the page.

In FireFox, I enable the option View / Zoom / Zoom Text Only.

Re: The worst program I ever worked on

#34
post #11

I worked with a guy (I won't name the company) who wrote Java code in one, huge, static class as much as possible. In fact, everything was largely in one function too. He decided to name his fields alphabetically. static int a static int b static String c static float d static int e... What, I wondered, would happen when he ran out of letters? Scrolling down further I saw this: static int aa static float ab static St…

I work with a guy, long time ago, who would take code already split into functions and refactor it into one big function. I am not joking here, actually happened.

Re: The worst program I ever worked on

#35
post #27

Earlier quoted context omitted.

That sounds kind of funny. Where do you go on error? One time I had to debug this incredibly obfuscated Word Basic subroutine. It was such a mess of gotos (deliberately so) that the company that wrote it for us thought they had us over a barrel and could charge us like a wounded bull. That is, until I showed my cow-orkers the superior technology of "paper, scissors and sticky tape".

Where do you go on error Hell, Arizona or any other village with that name. Real C# code can be like this: if(John is evil){ goto Hell}; ( http://msdn.microsoft.com/en-us/library/scekt9xw%28v=vs.71%2... )

GOTO HELL showed up with predictable frequency. I don't recall if he used it for errors, though.

Re: The worst program I ever worked on

#36
post #22
post #20

This is off topic but I find it difficult to read the blog-articles from jaquesmattheij.com . Zooming doesn't help because the text doesn't wrap correctly. Just a suggestion for the author to change the layout of the page.

You should try readability.com

But the fact that readability is suggested, suggests that the site isn't readable. That's a hint to the author that it needs to be looked at, which is what the grandparent comment says.

Re: The worst program I ever worked on

#37

The only place where the names made any immediate sense was 'main' and any C stdlib calls. Any job worth doing is worth doing right. Contrariwise, any job worth fucking up is worth fucking up stupendously. He didn't go all the way. #define monkeymeat printf #define turtlescrotum malloc #define wolfnipplechips gets #define chipotlaway exit ...

#define HEREWEGO { #define ENOUGHNOW }

Well we are diverging from the theme, but the proper form of that is

  #define O_HAI {
  #define KTHXBYE }

Re: The worst program I ever worked on

#38

The only place where the names made any immediate sense was 'main' and any C stdlib calls. Any job worth doing is worth doing right. Contrariwise, any job worth fucking up is worth fucking up stupendously. He didn't go all the way. #define monkeymeat printf #define turtlescrotum malloc #define wolfnipplechips gets #define chipotlaway exit ...

Not everything worth doing is worth doing well.

— Tom West, quoted by Tracy Kidder in The Soul of a New Machine (Modern Library, 1997). ISBN 0-679-60261-5

Note that Data General is defunct, so I take this quote as a warning.

References:

* http://en.wikipedia.org/wiki/Tom_West

* http://en.wikipedia.org/wiki/The_Soul_of_a_New_Machine

Re: The worst program I ever worked on

#39

I worked on a piece of code that literally drove the guy who wrote it round the bend. He had a mental breakdown, ran away, and eventually ended up in a different state ~3000 miles away. It wasn't so bad. Now debugging code written by Chemistry Students ... that's some scary stuff right there. Which is not to go all elitist and put Comp Sci degrees up on a pedestal, one of the better coders I've had the pleasure of wo…

You should try working with code written by hardware engineers. Those guys are extremely smart when it comes to digital and analog electronics, but never ever let them write a device driver ...

Re: The worst program I ever worked on

#40
post #11

I worked with a guy (I won't name the company) who wrote Java code in one, huge, static class as much as possible. In fact, everything was largely in one function too. He decided to name his fields alphabetically. static int a static int b static String c static float d static int e... What, I wondered, would happen when he ran out of letters? Scrolling down further I saw this: static int aa static float ab static St…

To really bork up the Java, you need a pattern fanatic. Once you stand working with Handler Adapter Handlers you know you should have taken the other colour pill.

Yes, i remember working for a company (java devs) where at some point we ended up having wrappers around wrappers around wrappers delegating stuff around, factories of factories ... It made your head spin.
Post reply on HN