Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
It's funny.  Laugh. Programming IT Technology

Programmers Hold Funerals for Old Code 342

MacBrave writes "The AP has an interesting story about how the programming staff at an Ohio company are holding funerals for retired or 'killed' programs. I dunno, this sounds a little TOO geeky for my tastes......."
This discussion has been archived. No new comments can be posted.

Programmers Hold Funerals for Old Code

Comments Filter:
  • by Anonymous Coward on Thursday November 04, 2004 @12:22AM (#10719987)
    Or do they bury it?
    • by Milo of Kroton ( 780850 ) <milo.of.kroton ( ... ail.com minus pi> on Thursday November 04, 2004 @12:24AM (#10720014) Journal
      I have similar ceremony, except commanded line "mv foo /dev/null"

      What can be sadder but than I tried use tab complete on /dev/null?
      • by Rufus211 ( 221883 ) <rufus-slashdotNO@SPAMhackish.org> on Thursday November 04, 2004 @12:58AM (#10720281) Homepage
        >mv foo /dev/null
        That's a terrible idea. You're actually replacing the /dev/null device with some random file, which will horribly kill things.
        • Re:Do they cremate? (Score:5, Informative)

          by Anonymous Coward on Thursday November 04, 2004 @01:57AM (#10720609)
          Actually, it depends on whether you have devfs and on mv's implementation. If you have devfs, then mv becomes copy and unlink, because rename doesn't work between filesystems. So, if you use devfs and mv is implemented to truncate, but not delete, destinations before overwriting them, then it would work. Though it would be quicker to just delete or shred the file.
        • by FlyingBeagle ( 159844 ) on Thursday November 04, 2004 @03:20AM (#10720955)
          I actually did this once. Our school's CS cluster was maintained partly by students, one of whom was me. I was, of course, very inexperienced in actual Unix administration, though I had read Slashdot, Usenet, etc., quite a bit. There was a directory in someone's home directory that no one could delete, even as root (probably due to some bizarre NFS issue, never figured it out). I had heard the phrase "send flames to /dev/null" and others in that vein. Plus I knew... er, "knew"... that /dev/null would always delete what you sent to it. Putting 1 and 1 together to make 3, I typed sudo mv undeletable_dir /dev/null.

          In the terminal room, there was suddenly a cacophany of beeping. The phone started ringing. This was bad. And no one knew how to fix it.

          Someone suggested rebooting the machine. Of course, the machine promptly refused to boot. Much panic was in abundance, the phrase "complete restore from backup" was ominously spoken. Finally, someone with a Clue (TM) showed up and pointed out that we only needed to remake the symlink from /dev/null to the actual device in /devices/pseudo/ (this is a Solaris system). Crisis averted.

          Moral? Several. man(4) null. Don't do things as root if you aren't sure what will happen. When you fsck shit up, try to find someone who actually knows what they're doing, and get them to fix it. And, above all, don't believe what you read on the Internet.
          • Not that you care now Im sure, but I have seen undeletable dirs on Solaris having to do with the automounter+NFS. Some weird deadlock occurs when you export an automounted directory over NFS or vice versa (I'm not quite sure, its been two years since I was a solaris admin -- or even used solaris).

            Also FS damage can prevent you from deleting things sometimes.

          • by dr_dank ( 472072 ) on Thursday November 04, 2004 @10:30AM (#10722870) Homepage Journal
            Our school's CS cluster was maintained partly by students, one of whom was me. I was, of course, very inexperienced in actual Unix administration, though I had read Slashdot, Usenet, etc.,

            Here's another moral: learning Unix administration on Slashdot is like learning emergency medicine by watching ER.
        • On a related note, cat /dev/null > myfile

          is a great way to truncate a file, especially if the file you're truncating is an apache error log that has grown out of hand.
      • by Rolman ( 120909 ) on Thursday November 04, 2004 @04:19AM (#10721217)
        I'd actually find the command "cat /dev/null > foo" a lot more spiritual, it's like Death coming for your soul. And hey, it doesn't even need to be god (root).
    • Flame war (Score:5, Funny)

      by 3770 ( 560838 ) on Thursday November 04, 2004 @12:36AM (#10720107) Homepage

      Well, I'll probably get flamed for discussing cremation but...

      pun intended.
    • by VeryProfessional ( 805174 ) on Thursday November 04, 2004 @12:58AM (#10720280)

      They had better not bury it...

      All those memory leaks could contaminate the groundwater.

    • by Siul1979 ( 820784 ) on Thursday November 04, 2004 @01:01AM (#10720295)
      How come nobody decides to recycle the printouts? :P
      • by glitch! ( 57276 ) on Thursday November 04, 2004 @01:23AM (#10720409)
        How come nobody decides to recycle the printouts? :P

        Because recycled printouts might lead to Microsoft code...

        (For those young 'uns, Bill Gates used to dumpster dive for old program listings to help his programming skills. Personally, I would prefer to learn from code the programmers thought worth keeping, and not what they threw away, but to each his own I guess...)
    • Re:Do they cremate? (Score:5, Informative)

      by neitzsche ( 520188 ) * on Thursday November 04, 2004 @02:07AM (#10720661) Journal
      I was recently in FOSS Oklahoma. I found their cemetery. Apparently they bury, not creamate. :-)

      If anyone is willing to mirror, my pictures (including the aforementioned FOSS CEMETERY) can be found under
      http://www.connelm.homelinux.com/foss/foss. htm

  • by DavidLeblond ( 267211 ) <meNO@SPAMdavidleblond.com> on Thursday November 04, 2004 @12:23AM (#10719992) Homepage
    10 PRINT "He's dead, Jim."
    20 BEEP
    30 GOTO 10

    RUN
  • by Evangelion ( 2145 ) on Thursday November 04, 2004 @12:23AM (#10719995) Homepage

    At the last place I worked, we retired a particular version of the application. We printed out the code onto paper, and all gathered around the project manager's barbeque and burnt the code, praying that we never, ever had to touch it again.
    • by pairo ( 519657 ) <gcbirzan@g[ ]l.com ['mai' in gap]> on Thursday November 04, 2004 @12:28AM (#10720052) Homepage
      Did you sit around a campfire and told stories about zombie processes too?
      • by plover ( 150551 ) * on Thursday November 04, 2004 @02:28AM (#10720769) Homepage Journal
        One night, these programmers I know were sitting around at our boss's house. We were in the backyard at the barbecue, drinking brews and roasting marshmallows over the printouts of an old, old modem driver. It was a night a lot like tonight -- the moon wasn't up yet, and it was pretty dark. One of them, Joe, said he heard a noise "like an orphaned process" coming from behind the arbor vitae shrubs. He went over to take a look, and never returned. We all thought he'd had too much beer and went home to sleep it off, so nobody worried about it too much.

        But the next day, Joe didn't show up at work. And the day after, and the day after that. We began to wonder if there wasn't something amiss, but our boss wouldn't say anything about him. I called him at home, but just got his answering machine.

        Well, we got suspicious, so one lunch hour we snuck out and went over to the boss's house to check around the shrubs. You know what we found behind that arbor vitae tree? A condom laying outside the window! And you know what we saw when we looked in the window? Joe and the boss's wife in an embrace! He'd been fired for sleeping with her!!!!

        Or maybe I just drank the beer and imagined the whole thing...

    • by Anonymous Coward
      Back in the late 1960s, we did this at Caltech, where an IBM7090/7094 handled all computing for the university and NASA JPL. We burnt some of the plastic flowcharting templates. The smoke triggered the overhead fire sprinklers. Whooops!

      Professor Jonathan Vos Post

      http://magicdragon.com/math.html
    • I eulogized my aged server a couple years ago here [slashdot.org] on Slashdot in my journal. Does that count?
  • by Squigley ( 213068 ) on Thursday November 04, 2004 @12:23AM (#10720000) Homepage
    #!/bin/sh
    echo "first post"
    • done! (Score:5, Funny)

      by DarkMan ( 32280 ) on Thursday November 04, 2004 @01:23AM (#10720407) Journal
      package troll.slashdot;

      import java.io.Writer;
      import java.io.PrintWriter;
      import java.io.IOException; // Retires an obsolete shell script

      class Main {

      int static main() {
      OutputRoutine or = new OutputRoutine(System.out);
      TextGenerator tg = new TextGenerator(or);

      tg.run();
      }

      } /* Closes: class Main() */

      class OutputRoutine {
      private PrintWriter pw;

      OutputRoutine (Writer w) {
      this.pw = new PrintWriter(w);
      }

      void Output (String text)
      throws IOException {
      pw.println(text);
      }

      } /* Closes: class OutputRoutine */

      class TextGenerator {
      OutputRoutine or;

      TextGenerator(OutputRoutine or) {
      this.or = or;
      }

      void run() {
      or.Output("First post");
      }
      } /* Closes: class TextGenerator */
    • by Anonymous Coward
      are you suggesting we play the 'Last Post' to the 'First Post'
      ?
  • Sure, but (Score:5, Interesting)

    by Anonymous Coward on Thursday November 04, 2004 @12:23AM (#10720002)
    Sure, they may not be people, but it's easily comparable to a pet's funeral. They didn't have a so-called 'soul', nor were they human. However, they meant a lot to us, regardless of their intelligence.

    I think the same could hold true for a program. Admittedly, I've never had an emotional connection to any of my programs, but I know a few people who might actually love their code, and I could sorta-kinda-not-really-but-ok-it's-your-choice understand.
    • Re:Sure, but (Score:5, Insightful)

      by Anonymous Coward on Thursday November 04, 2004 @12:27AM (#10720041)
      it's easily comparable to a pet's funeral. They didn't have a so-called 'soul'

      Posting AC given the number of religious nuts like to be reading this topic and what I'm about to say... anyway, I don't see how you can compare a living, breathing animal to a bunch of binary output. Other animals have at least as much chance of possessing a soul as we do -- which is pretty fucking small in my opinion -- but code is still manually assembled.

      • compare a living, breathing animal to a bunch of binary output. Other animals have at least as much chance of possessing a soul as we do -- which is pretty fucking small in my opinion -- but code is still manually assembled.

        And so is fictional writing, and pretty much all other forms of art. Stuff you've worked on, sweated over, cried over, stressed over. When it is necessary to set such a thing aside, it can be a loss, of momentary purpose if nothing else.. I've gotta stop posting drunk.
    • by Epistax ( 544591 ) <<moc.liamg> <ta> <xatsipe>> on Thursday November 04, 2004 @01:06AM (#10720320) Journal
      A pet has more of a soul than any anonymous coward.
    • by plover ( 150551 ) *
      Hey, my code has soul. More soul than the neighbor's little f'ing yap-o-rama dachshund, anyway.

      In related news, anyone want to go to a dachshund funeral? They'll probably need to schedule one next week sometime.

    • Of course animals have a soul. It's what makes the difference between a living animal and a dead one. What you possibly meant to say is that they don't have a sentient soul. According to the jewish religion everything has a soul, and more then one. They go in layers: First the soul that means the object exists (like a rock or an atom). Then the soul that gives life (like a plant). Then the soul that give movement and will/desire to do something (an animal). Then the soul that provides speech (also senti
    • Of course animals have a soul. It's what makes the difference between a living animal and a dead one.

      What you possibly meant to say is that they don't have a sentient soul.

      According to the jewish religion everything has a soul, and more then one.

      They go in layers:

      First the soul that means the object exists (like a rock or an atom).
      Then the soul that gives life (like a plant).
      Then the soul that give movement and will/desire to do something (an animal).
      Then the soul that provides speech (also sentience),
  • ASP.NET (Score:5, Funny)

    by BladeMelbourne ( 518866 ) on Thursday November 04, 2004 @12:24AM (#10720004)
    I cant wait for the day that ASP.NET has it's funeral... so I can pay my disrespects.
    • Re:ASP.NET (Score:5, Funny)

      by cujo_1111 ( 627504 ) on Thursday November 04, 2004 @12:28AM (#10720045) Homepage Journal
      You can't terminate ASP.NET without first killing off it's parent ASP.

      It will only breed and start again...
    • Re:ASP.NET (Score:5, Funny)

      by Stevyn ( 691306 ) on Thursday November 04, 2004 @01:09AM (#10720335)
      I can't wait for the windows 98SE code to be burned. Just imagine the glow and warmth of 328,304,203 sheets of paper burning. Then it will burn out of control and they'll try smothering it with the code to Windows Me.
      • Re:ASP.NET (Score:2, Funny)

        by Anonymous Coward

        This message is brought to you from the Department of Homeland Security. Please stop giving arsonists/terrorists new ideas. They're doing just fine without your help. Thank you that will be all.

        Slashdot User ID 691306 added to blacklist
        Slashdot User ID 691306 added to no-fly list
        Slashdot User ID 691306 added to monitor-ip-traffic list
        Slashdot User ID 691306 added to bug-your-phone list
        Slashdot User ID 691306 added to track-via-hidden-gps-transmitter-in-rectum list.
        Please NOTE: These additions are for your

      • Re:ASP.NET (Score:3, Funny)

        by Anonymous Coward
        Is that the entire code to ME or just the diff of 98?

        - echo "Starting Windows 98"
        + echo "Starting Windows ME"
        - LoadBloatedUI();
        + LoadSuperBloatedUIItsBetterHonest();
        - I = Random(50)
        + I = Random(2);
        if I = 1 {Crash();}
        + Pray();
  • by jsav40 ( 614902 ) on Thursday November 04, 2004 @12:25AM (#10720027)
    The 'dead' programs represent a chunk of those coder's lives and a fitting sendoff provides closure for the 'parents' of that code.
  • TOO Geeky? No way! Just look at this: http://slashdot.org/article.pl?sid=04/05/01/183721 5Z [slashdot.org]
  • Eulogy (Score:2, Funny)

    by Anonymous Coward
    It was such a nice program . . . sniff sniff. I remember when I wrote this line here . . . fixed a bug that crashed the server.
  • by Dancin_Santa ( 265275 ) <DancinSanta@gmail.com> on Thursday November 04, 2004 @12:28AM (#10720051) Journal
    God knows how many times I've sat in front of my source code knowing that not only could it be made better, but that there is probably a better way to do it. Unfortunately, the reason old code stays around hobbling around the system with plaster casts around its legs and band aids covering its heads, yes more than one head because at some point I figured that it would be better to stick a brand new head on there rather than refactor the functionality out and create a brand new program. No, reuse of old code is like the Jesus of programming. No matter how dead and in the grave Lazarus.exe may be, somehow we can reach in and squeeze just a few more years of life out of the system be applying just another patch, just another incantation. Lazarus, come forth! When in reality, it would have been better to leave that rotting corpse in the grave.

    A ritual like they describe in the article seems like a really good way of encouraging long-needed rewrites and the tossing out of old code. Good code lives on, always young and fresh and rosy fingered. Timeless, never aging, good code does its job and does it well. Good systems are built around good code and intuitive use cases are built around good systems. A system that needs constant tweaking and patching and magic to keep it going is a system that is hopelessly falling towards the tomb. Better to print that code out and bury it in the cemetary and replace it with good code than to find another way to keep the herking and jerking system from collapsing under its own weight.
    • Definitely (Score:5, Insightful)

      by tqft ( 619476 ) <`moc.oohay' `ta' `ua_sworrubnai'> on Thursday November 04, 2004 @12:45AM (#10720182) Homepage Journal
      Isn't the real advantage of a decent burial of the code showing "respect" to the programmers who may well now be senior management?

      That way you can send invites to the original programmers saying if you wish to attend the laying to rest of the veritable workhorse which held up x, y and z parts of the company for 10 years and helped make $Xm.

      Rather than having boss/PHB come in and say why does the VP IT access to the database no longer work? As he has been using a backdoor from 10 years ago. Or the VP comes down and says why are you deleting $Xm code investment (ie his OT bill from playing TrekWar).

      Besides if the VPs show up you can get in some good schmoozing (sorry networking) so they know who you are when bonus time comes.

      Never (ever) surprise management.
    • I've sat in front of my source code knowing that not only could it be made better, but that there is probably a better way to do it. Unfortunately, the reason old code stays around hobbling around the system with plaster casts around its legs and band aids covering its heads, yes more than one head because at some point I figured that it would be better to stick a brand new head on there rather than refactor the functionality out and create a brand new program.

      Old code has much embedded wisdom. Lots of l
  • bad signs (Score:5, Interesting)

    by ebunga ( 95613 ) on Thursday November 04, 2004 @12:32AM (#10720085)
    Back in the early 90's, the department my father was in held a funeral for the ampersand in their Lotus Notes email addresses. Yeah, they were the hardcore nerds of the company... dealing with Generation and Transmission at a large power company. Unfortunately it was also a sign that the entire department was about to be laid off.
  • by jmcmunn ( 307798 ) on Thursday November 04, 2004 @12:37AM (#10720123)

    Copy the directory to a folder to be backed up (or burn it on a CD) Delete original code.

    OR

    Make sure all old outdated code is surrounded by /*
    Old dead code...
    Insert profane comment here about how crappy the guy is who wrote it if it's not mine
    */

    And save it for later reference. No telling when I am going to need to scam some of my old code when I am in a hurry some day. :-) Or shit, just when I realize I am writing the same routine again and don't feel that creative juice flowing.
  • jesus.exe:

    ......
    revive("3 days");
    ......

    • by cas2000 ( 148703 )
      runs on any host with jesus installed:

      #! /usr/bin/jesus

      cp -f $0 /dev/other_believers
      install -m 755 brain /dev/skull || die

      (other versions available for different religions)
    • by Anonymous Coward
      JesusFollowers.exe

      while( IQ 100 || Redneck == true )
      Vote( "Bush" );

  • by ewe2 ( 47163 ) <ewetoo@gmail . c om> on Thursday November 04, 2004 @12:40AM (#10720148) Homepage Journal
    The temptation to keep old code to save the effort of reinventing the whole approach is very real. Most programmers maintain code, not originate it. So actually burying or burning the printout is more than just symbolic, it's a real attempt to shift the mindset. IMHO it's very needed.
    • How do you get three days going from friday afternoon to sunday morning?
    • Right now I'm rewriting several thousand lines of dlsh script. It's been a legacy I've had to deal with for five years now, and I've finally gotten tired of it. No one uses dlsh. It's archaic. It's not sh based, it's not csh based, it's or horrible proprietary shell existing in a world where proprietary shells do not belong.

      So Monday my boss asks me what I'm doing:

      Boss: "What else is up besides the ABC project?"

      Me: "I'm rewriting the XYZ script in bash."

      Boss: [stunned silence] "Is that necessary?"

      Me: "
    • It takes a lot more effort to redo the whole thing, in most cases, than it does to just fix the problem in the existing code. Now certianly sometimes it's needed, old code can get so hacked up that it doesn't do it's job well and takes forever to modify, but I think many programmers get way too rewrite happy.

      Part of the problem is that they think that they can rewrite the code to a perfect state. That whoever did it before was stupid, but with their rewrite it'll be so easy to maintain and expand. Of cours
  • Scary Quote (Score:5, Funny)

    by BottleCup ( 691335 ) on Thursday November 04, 2004 @12:41AM (#10720157) Homepage

    "Some things die gracefully and other things we've had to kill," Perseghetti said.

    Can anyone say Programming Mafia?

  • The graveyard has been part of LexisNexis for a very long time.. I've been employed there for 9 1/2 years now. Its really kind of cool to see.
    • I quit after programming 7 1/2 years and now go to law school.
      By the way, Lexis is definitely better than westlaw.
      Ever thought of a tool that when you enter a citation, you set an optionnto get that case and all the cases it references, and all the cases they reference, in like a tree mode with the short summary? Maybe some option to set how many levels deep it goes?
      Also, how about an easier way to copy the deep link to cases for when you're doing research?
      I hate when non-techs try to give me progra
  • by YU Nicks NE Way ( 129084 ) on Thursday November 04, 2004 @12:47AM (#10720202)
    Last summer, a group of developers from a company based here in the Puget Sound area held a funeral for a particular subsystem which was being retired with extreme prejudice. They went to a park in the southern part of Bellevue, and carefully layed out a CD containing the source code for the product on top of a pyre of shrink wrap boxes for clients of this particular piece of server code. They held a proper wake for the late unlamented, and then, with kerosene and some matches, sent it on its way to a different, if not necessarily better, place.

    Unfortunately, it was about 35 Celsius that fine July day, and there was a burn ban in place throughout King County. The neighbors did summon the department of fire protection, and did also summon the department of police protection. Hilarity ensued, I am told, while the hapless coders ran around trying to extinguish the blaze and eliminate the evidence before the arrival of those two fine force of Washington State's best.

    (No, this story does not refer to employees of Microsoft. I wish it did, as that would make it better still -- but I'm afraid that geeks who live indoors are much the same everywhere.)
  • by Infonaut ( 96956 ) <infonaut@gmail.com> on Thursday November 04, 2004 @12:49AM (#10720213) Homepage Journal
    I understand something of what's going on in the minds of those folks. It's geeky and a bit weird, but sometimes you have to pay tribute to things (whether material or abstract) that have been a big part of your life.

    In my case the soles of both boots cracked to such a degree that my green wool socks actually squirmed out and were visible. This is generally not considered very professional in military circles, so I had to go for my second pair. But this pair had been with me for something like four or five years, and it pained me to see them go. They were so comfortable, they felt more like hide on my feet than actual boots. They'd been to Ft. Irwin, Ft. Ord, Ft. Benning, Ft. Drum, Jungle Warfare School in Panama, and they finally died in Africa.

    So after I retrieved by backup pair, I gathered a few guys, walked over to the trash pit, threw some gasoline on the old pair, and burned them while holding a salute. One of the guys played 'Taps' in Bobby McFerrin fashion.

    People do weird things on deployment, but to bring it back to these programmers, when you're in the trenches (be they corporate or otherwise), sometimes it's important to engage in a bit of anthropomorphizing.

    Or perhaps these guys in Ohio are nuts, and I am too.

  • by prockcore ( 543967 ) on Thursday November 04, 2004 @12:50AM (#10720220)
    we'll be holding services for their social lives.
  • by danb35 ( 112739 ) on Thursday November 04, 2004 @12:51AM (#10720230) Homepage
    I saw the /. writeup, and thought it sounded like where I work. Surprise, it is! Not as a coder, though.
  • bah i'd go (Score:2, Funny)

    by Anonymous Coward
    regardless of how geeky i might think it is, i'd probably go, mostly for the cake.
  • Comment removed (Score:5, Informative)

    by account_deleted ( 4530225 ) on Thursday November 04, 2004 @12:55AM (#10720260)
    Comment removed based on user account deletion
  • First thing that came to my head was I wonder how they put to rest MS Bob, and I googled for it and thought this was kinda funny and relevant.
    "During his short, unhappy life, Bob was ridiculed, ignored and finally abandoned.
    ...
    Sure, he was only a computer program, but still: Let us now pause a moment to pay our respects to Microsoft Bob.
    RIP: Bob, 1995-96"
    source: Bob is dead; long live Bob [post-gazette.com]
    • Assuming what you describe is true, the fact you know this is kinda scary. Not in a bad way.

      What about lesser but equally wonderful things, like the fact that Macromedia basically SHELVED several programs (such as Fontgrapher) and never sold the the code for someone else to bring into the world of OSX, OpenType, and complete Unicode?

      HMmmmmmm?

      How many other wonderful apps coulda been contenders except for the second most common resource in the universe: corporate myopia?

      TELL ME? What do I HEAR?

      (some

  • old code never dies (Score:2, Interesting)

    by updog ( 608318 )
    it always gets recycled.
  • by bboyers ( 21742 ) on Thursday November 04, 2004 @01:18AM (#10720389)
    10) I merely inherited this code, but I'm not responsible for it.
    9) All the developers of the original code have been laid off, so we need to rewrite it to understand it.
    8) Sorry, IT has no more maintenance hours to support this application, but we still have development hours to rewrite it.
    7)[insert new tech buzzword here] is the future, the old platform of [insert old tech buzzword here] is passe.
    6) If we rewrite the application, we'll have more features, less cost, and better quality...I promise.
    5) What were they thinking, I have a clear vision of the solution now.
    4) What was I thinking, I have a clear vision of the solution now.
    3) The customer changed the requirements and a rewrite is required.
    2) Prior mismanagement lead us to this position, but the current management can support us in this rewrite.
    1) I need to justify my job, this application should be rewritten.
  • by jejones ( 115979 ) on Thursday November 04, 2004 @01:19AM (#10720393) Journal
    ...shouldn't it be "Reboot Hill"?
  • by Anonymous Coward on Thursday November 04, 2004 @01:32AM (#10720456)

    This is so embarassing to the rest of us that work there. I've been writing software at LN for almost a decade and have NEVER heard of this. Where did the AP dig this crap up? One little group out of several thousand programmer employees decides to be incredibly stupid, and the rest of us have to wear "Complete Retard" stamped on our foreheads. I only hope this can be lived down before I have to look for another job. Christ, I'm going to find these people's cubes and bury THEM. "Blocker Hill", indeed. Shoot me now.

    And to those jackass apologists here (jsav40, Dancin _Santa, ewe2) who say "it's not TOO geeky or bizarre", fuck you. You don't work there.

  • by Cryptnotic ( 154382 ) on Thursday November 04, 2004 @01:36AM (#10720477)
    We had been working about two years on this embedded Linux system. The project had been fraught with difficulties mainly related to a poor platform choice. Anyway, the project was almost completely finished and ready to go into production. Literally a week later management decided to cancel it to sell the customer on buying our next-next-generation product instead.

    We held a bit of a ceremony where we poured out some malt liquor for our killed project.

    I don't work 60 hour weeks anymore. These days I'm more reasonable.

  • Clippy (Score:3, Funny)

    by tuxter ( 809927 ) on Thursday November 04, 2004 @01:37AM (#10720483) Journal
    Please please burn clippy, or smelt him, or make him into a toothpick. But please
  • by suso ( 153703 ) on Thursday November 04, 2004 @01:41AM (#10720515) Journal
    While this may sound like taking things a bit too far. If you can think ahead to when AI is all around us. Would we have funerals for family robots that fail or are "killed" in some way? Maybe this is the first inclings of those types of things.
  • I didn't know LexisNexis was in Dayton.

    Maybe while they're at it they can hold a funeral for American Democracy.
  • I was thoroughly expecting to see the server slashdotted and then to read all of the witty comments about holding a funeral for a dead webserver.

    Alas, the server's up, so it's apparantly not meant to be.

    *sigh*
  • by Rolman ( 120909 ) on Thursday November 04, 2004 @04:06AM (#10721134)
    I have seen many cases of people holding funerals or paying their respects to renowned pieces of code or equipment. IIRC, even Bill Gates and co. paid theirs to MS-DOS in the Windows 2000 presentation, when the command 'exit' was typed on a DOS virtual machine.

    But the funniest I've ever seen is when I visited a good friend of mine in a software development company during the dot-com era (lots of young geeks around), he was showing me the office and all that, then he took me to the backyard/graveyard, where they had several things buried, but the most recent one was a modem (they were also an ISP), complete with a tombstone and an epitaph that read "NO CARRIER".
  • by forii ( 49445 ) on Thursday November 04, 2004 @04:10AM (#10721154)
    I worked for 5 years at a video game company that had a peculiar kind of Revision Control. Generally, the newer you were, the less of the game you worked on, and so if you were a new hire with no experience, the tradition was that you created your own source code file named after yourself. Then you would write your code, and then ask the Lead Programmer to put hooks in the main code. This essentially kept new programmers from screwing up the rest of the game, which was important because we were almost always on a time crunch (doing 2 releases a year).

    Over time, as you became more familiar with the code and the game you were given more responsibility over more of the code, until as Lead Programmer the entire project was your domain. If you left the project, though, there was usually nobody to maintain the code in your "name file", and as routines got re-written/moved/deleted, the name files would shrink in size, and then one day be deleted entirely. In this way they acted as sort of a historical record of the people who had worked on the project.

    Over my five years, I had worked my way up to Lead Programmer and then moved on to different pastures. I still kept in touch with my old co-workers, and 3 years later I got an email from one who told me that they had finally removed my file, "forii.cpp" from the Makefile.

    My source code file from when I had started at the company had by this time just been reduced to a single small routine and a lot of commented out code, so it wasn't a tough decision. But I still felt a tinge of sadness, as it felt a little like being written out of the history books.
  • by MORB ( 793798 ) on Thursday November 04, 2004 @05:27AM (#10721509)
    There was a filesystem repairing utility on old versions of AmigaOS called diskdoctor. This thing was awful, and you ended up with a blank floppy or an even more screwed one most of the times you used it. I recall an interview from one of the amigaos guys, where he explained why it did disappear from later version of the os. As they were pondering whether fixing it or removing it, they got an idea: letting it choose its own fate. They put the source on a floppy, erased it from their harddisk, then ran diskdoctor on the floppy. The filesystem got screwed and the sources lost. It had just commited suicide.
  • Closure is good (Score:5, Interesting)

    by theonetruekeebler ( 60888 ) on Thursday November 04, 2004 @07:48AM (#10721976) Homepage Journal
    One of the most depressing moments of my career as a programmer was when I found out that an application I had worked on for almost four years was being retired. Worse yet, it was being retired because some nitwit Y2K consultants had declared it to be broken and offered to rewrite it for an insanely large amount of money. The Y2K consultants lied.

    Later I learned that a data warehouse I had spent two years building was being cancelled because the client didn't want to spring for additional drivespace. About that time the startup for whom I'd worked a year of 60-hour weeks laid off all its programmers, deciding that its patent portfolio was more profitable than its actual product.

    Today, not a single line of production code that I've written is running anywhere.

    What depresses me is that I had been pouring my heart and soul into something so ephemeral, that all my hard work was being thrown away and obsoleted. It still saddens me greatly to know that my career has left no lasting mark on the world.

    • Re:Closure is good (Score:4, Interesting)

      by tootlemonde ( 579170 ) on Thursday November 04, 2004 @04:00PM (#10727339)

      What depresses me is that I had been pouring my heart and soul into something so ephemeral...

      Make sure you learn something important or useful from every project. That way, no matter what happens to the project later on, you carry some benefit with you forever.

      Sometime what you learn is only something not to do in the future or that something you were sure was true was in fact completely wrong.

      One thing I've learned is don't work 60-hour weeks unless you get paid for overtime. If you do get paid for overtime, work as many 60-hour weeks as you can because there may be many 0-hour weeks in the future.

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...