Golabutron 3000
The Bastich
Index

[Spring 1997] LabZombies.Part(1);

Originally published on Wednesday, April 9, 1997 in CSU Chico's The Orion student newspaper. View Archive Page.

Commentary

The Helpdesk saga continues with a Lab Zombie sub-thread!

At the beginning, Bastich is looking forward checking the Lurker's Guide to Babylon 5, an insanely-thorough fan-run website that predates the zillions that now exist on Fandom.com and other services. There were detailed episode synopses (i.e. spoilers), analysis, speculation, and TONS of behind-the-scenes dirt from JMS, pulled from his posts across CompuServe, Usenet, and other pre-social media forums. I started watching B5 with Season 2, so the Lurker's Guide was how I got caught up on all of the threads (since in these days, there was no way to watch prior seasons unless you knew somebody who recorded them on VHS).

I didn't coin the term "Lab Zombies" but I can attest to their existence, especially after I started patrolling the computing building as part of my duties. People were glued to their workstations and often had to be dragged out kicking and screaming at closing time. Sometimes they were desperately cramming to finish a programming assignment and sometimes they were just hanging out or basking in the faster internet compared to the dial-up they had at home. It wasn't fun throwing people out, but it had to be done before I could clock myself out.

The zombies at the end are partaking in the following nerd activities:

  • MUD (Multi-User Dungeon)
  • IRC (Internet Relay Chat)
  • Perl (Programming Language)

NOTE: I want to be up-front that the titles of these four strips (LabZombies.Part(x);) are complete gibberish. It looks kind of like Java, but violates Java best practices in a few ways:

  • Capitalizing LabZombies implies this is a static class method which is fair enough, but LabZombies seems like an overly-specific class. It probably should be an instance of a more general ComicStrip.
  • Method names should be lower Camel Case (start with a lowercase letter).
  • Method names should be verbs that clearly explain what the method is doing (so Part implies that something is going away, but it's ambiguous).

This would have been better, albeit still problematic.

labZombies.getPart(1);

Transcript

TITLE The Bastich By Hart

PANEL 1 (BASTICH leans eagerly toward his Helpdesk workstation.) BASTICH: Okay, sir, the changes to your account will take effect in thirty minutes... no problem... bye. Ah, finally, a little peace and quiet. Time to catch up on the Lurker's Guide.

PANEL 2 (It suddenly goes pitch black with only BASTICH's glasses visible.) SFX: BZZZT--! BASTICH: What-!? A power failure? How inconvenient.

PANEL 3 (Still only BASTICH's glasses are visible.) BASTICH: Now all of the workstations will have to reboot, and I'll have to sit here and tell 5,000 users that it wasn't an e-mail virus that crashed the system...

PANEL 4 (BASTICH is now silhouetted against a background of RING sound effects.) BASTICH: Okay, here we go... At least the backup power should be kicking in soon...

PANEL 5 (BASTICH is still in deep shadow as the lights come back on.) BASTICH: Yeah, here it comes... SFX: CHNG BASTICH: Looks like the worst of it is over...

PANEL 6 (BASTICH reacts in shock as a horde of zombies approach the Helpdesk.) BASTICH: ..or maybe not. ZOMBIE 1: MUD connection lost. Ugh... would've made 17th level Mage... ZOMBIE 2: ...HotChk needs me on IRC... ZOMBIE 3: Must... write... Perl... BASTICH: The LAB ZOMBIES have emerged! CAPTION: TO BE CONTINUED...

CREDITS Bastich (c) 1997 Joshua Adam Hart