Article: 149446 of alt.sysadmin.recovery Newsgroups: alt.sysadmin.recovery Subject: Unevolved Troglodytes bakcward-R Us Approved: Preaching to Uncle Ben's Converted From: henke@kharendaen.krall.org Message-ID: Lines: 123 X-Newsreader: Gnus v5.7/Emacs 20.6 Date: 24 Jun 2000 12:37:05 -0500 NNTP-Posting-Host: 209.113.100.246 X-Complaints-To: abuse@insync.net X-Trace: insync 961869631 209.113.100.246 (Sat, 24 Jun 2000 13:00:31 CDT) NNTP-Posting-Date: Sat, 24 Jun 2000 13:00:31 CDT Organization: Insync Internet Services, Inc. Path: b4.mv.meer.net!Usenet!feed2.newsfeeds.com!newsfeeds.com!news-peer.gip.net!news.gsl.net!gip.net!europa.netcrusader.net!209.113.65.250!korova.insync.net!insync!not-for-mail Xref: b4.mv.meer.net alt.sysadmin.recovery:149446 Them: You know that piece of paper you gave us like three months ago? Me: Them: That vacation notice? Me: Yep. Them: That said you would be on vacation? Me: Yep. <"What the fuck else would a vacation notice possibly say?"> Them: That you've been reminding us about for the past two weeks? Me: That's the one. <"It's not like I've taken any _other_ vacation in the past two years."> Them: It says your vacation starts tomorrow. Me: Yep. <"Wow. You have a phenomenal grasp of the obvious for a mental midget."> Them: So you won't be here? Me: Yep. <"Got it in one, Socrates."> Them: How can we reach you while you're gone? Me: You can't. That's what "vacation" means. It means I will not be at work and that I will not be on call. Vay. Cay. Shun. Them: But what if we need to? Me: I have written a handover document for $PROJECT. It contains everything you need to know to support it. The sources, the user docs and the internal docs are in the CVS tree. You were told about all this over a month ago. Them: But I don't know how to $TRIVIAL_THING! Me: That is explained in both my step-by-step procedures document and the man page for $TRIVIAL_THING. <"... and a trained slug could figure it out from first principles in about an attosecond."> Them: [paraphrased] But how will my work get done when you're not here to do it for me? Me: You could try doing it yourself. Them: But I don't know how! Me: Learn. It probably would have been a good idea to start learning it three months ago when you found out you'd need to know it <"or sooner, since it's your fucking job, moron">, but since you didn't you'd better start now. It shouldn't take more than <...figure for the dumbest dipfuck on the planet, double it, add one, convert to the next larger unit...> a few hours. Them: Well, just do $OTHERTHING for me then. It only takes about two hours. You'll be here at least four more. Me: Those hours are already spoken for. I can spare you about ten minutes if you've tried to do it yourself and get stuck. Them: You aren't being very helpful! Me: Go talk to $PHB then. If you can convince him that when he told me to work on $IMPORTANT_THING he actually meant that I should ignore it and do your work for you instead, I'll be happy to. Repeat at about the rate of about one cow orker per hour. ObBonus: Me: Don't use // for comments in C programs. That is a C++ comment, not a C comment. Use /* */. Them: But it works. I use it in all my C programs. Me: It works with gcc as a non-standard language extension. You will get warnings about it if you compile with the recommended compiler options for this project. Them: I turned those off. I got too many warnings. It works fine. Me: You're supposed to fix the warnings. They are usually important. Them: I did. I fixed them by using my own CFLAGS. Me: Don't. And don't use //. It isn't C. Here are three textbooks that say so. Here is the language standard. Here is the FAQ. Them: But it works fine. Me: It works now with a particular compiler if you mangle the options. Them: I'm doing it my way. --< time passes >-- Them: The ProC pre-processor for snOracle barfs on my program, look! Me: It doesn't understand C++ comments. Them: How do I fix it? Me: Use C comments. Them: But I like using //. How do I make ProC accept it? Me: Go read the docs. You probably can't. It is a C compiler and what you are writing is not C. Them: But it works fine. Me: No, it doesn't. That's why you're here, remember? -- Mail to henke "recovery == places with no phones at all" at insync dot net.