Wizard needs ninja skillz, badly.

MEMO TO ALL EMPLOYEES

Please remember that Section 4c of the $MegaCorp employment contract specifically prohibits bringing weapons or objects which could be used as a weapon onto any $MegaCorp premises at any time. For further information on $MegaCorp policies concerning weapons and employee safety please click here.

Technically I'm banned from the office because I'd be happy to beat quite a few of my cow-orkers senseless with my laptop and strangle them with a USB cable.

Some cow-orker decided to ask a specific question of a general audience rather than contacting the I18N team who actually know their asses from a hole in the ground when it comes to what characters might be included in a Chinese codepage. She's new and can be forgiven for this. The super senior PM guy who doesn't know diddly about things international or language-specific is another matter.

When asked about a Chinese system needing to also display English his response was "This sounds almost impossible! You have to find a codepage that'll have both the English and Chinese character sets in." Which is every single fucking Chinese code page in existence, from MS936 & 950 to 2312 and GB18030. ALL codepages have 7-bit ASCII as the first 128 characters, even all the Unicode translatíons.

Now his ignorance of this isn't the biggest problem (even though he should have passed on the question to the person in his department who actually works with I18N). It's that he then argued when corrected by the guy his own colleague asks such questions of: me.

I might expect this to work in a Unicode deployment, but anything else I'm fairly sure would fail.

Because he's an expert in... nothing, actually. He deals mainly with Java and scripting shit and even then, despite being Senior Director, has no actual specialisation other than spreading misinformation and pissing me the fuck off.

Which goes a long way to explaining why $MegaCorp needs to have a written, continuously publicised anti-weaponry policy.

EVERY SINGLE COMPUTER CODEPAGE IN USE TODAY -- EVEN ON MAINFRAMES AND (cr)APPLES -- INCLUDES BASIC ASCII.

The Stupid Hurts

I've been gone for a while. It started with being sick, then going to a course, then vacation, then getting sick again and by that time moving to a happy place. I've been in such a very happy place that I haven't been able to muster the anger necessary to write about this shit. Until today...

I hit the lottery and then some. This dog's got a new bitch. The downside is that as bad as shit is here at $MegaCorp, I'm doing the Obama brush-it-off-my-shoulder routine because she makes me that happy. Lassie's not here today, though; she's gone all week at a conference. Even that I can handle but yesterday I got stuck with a ticket from $CountryCo and the chinks in my new, non-unhappy MildlyAnnoyedPuppy armour appeared.

Need help for Disaster Recover(DR) installation?
Is it possible to install $YourBigApp with out accessing the database server?
What type of parameters we need to set in DR setup?
Please do the needful by reply today.

What the fuck? It's bad enough that he doesn't know the difference between DR and HA (high-availability) but this pigfucker wants to install what's more or less a giant fucking front end for a database without actually having a database.

Dear Pigfucker,

You write that you've installed $OurBigApp successfully before and you must therefore know that access to the database is required for this. What would you do with a database front-end application which can't connect to the database?

[explanation of HA and methods of implementation]

Love,
REC

And that should've been the end of it. I went home and ReallyBadDoggie-styled Lassie one more time before she left for her conference and the world was again good.

Until today.

I'd already woken up in a foul mood with a hangover from drinking Kölsch beer last night and no hot bitch asleep on my shoulder meaning no morning festivities before I left for the Panopticon. I arrived to find a response from Pigfucker.

As we have told you we have installed $YourBigApp in all environment with database access.Now we need to have the DR environment wherein we need installation of $YourBigApp .But we are told that we won't have database connectivity.According to our understanding,while installing $YourBigApp ,it asks for database connectivity.So we are not sure as to how we can go forward with the installation without the database connectivity.
Secondly we are told that we need to have a clone of Production environment.We have checked in knowledge base and have not found any document regarding this.So, can you pls inform about the process of cloning an existing $YourBigApp environment.

Lassie is fond of saying, "Stupid should be painful," and she's right. Unfortunately it's usually their stupid and my pain. I hadn't missed its comforting shape but I returned my noggin to the my-head-shaped-dent in front of my keyboard.

You cannot "go forward". You can't go backwards. Without a database to connect a database front end to you cannot move. You cannot install $OurBigApp without database connectivity. You cannot use $OurBigApp without database connectivity. Without a database containing data $OurBigApp can't do anything.

That you were told by your management you need $OurBigApp to be cloned in no way requires us to design a method to do so. $OurBigApp has no method for cloning environments. By its very nature it cannot be cloned.

This ticket is closed.

Our internal application was "upgraded" over the weekend and I searched desperately for my Root Cause: 17-Fuckwit but this important change, like so many others, didn't make the cut.

I'm back.

Weird Al

I love the film UHF. It had just the right amount of stupid and did a good job at parodying both TV and en entire genre of cheesy films which people like Adam Sandler still insist on making. As a bonus Victoria Jackson gets a lot of screen time.

Watching that film is one thing, living its vignettes is another.


I haven't had a ticket which could be considered even remotely interesting in over a month. What I've had are a bunch of fuckwits who watched this and thought it was a training video:


Update: embedding this vid was killed. Have a direct link.

A smattering of examples:

Do we need to mount the File System on Unix if it is located on Windows?

Nah. You just need to swap polarity on the network cables.

We do not understand, whether this user preference is some kind of server preference parameter, or if it is stored, in the CONTACTS table or what

You think -- despite my explanation -- that employee user preferences might be stored in the customer contact tables and you insist on appending "Systemwide and Database Engineer" to your name on all mail? The title alone speaks volumes.

Or this exchange:
Corp: Do you support 64-bit Windows 2003?
REC: No.
Corp: When will you support it?
REC: Never.
Corp: Why not?
REC: We don't process and calculate, we just move tons of data.
Corp: But we want 64-bit Windows
REC: Why?
Corp: Because it's 64 bits!
REC: And that's better because... why?
Corp: Because it's more than 32, duh! ESCALATE! MONKEY TOO STUPID TO REALISE 64 IS TEH BETTAR OF 32.
REC: You want to buy new hardware and a new OS to run our software which won't, in fact, be able to run our software half as well as your current hardware.
Corp: Yes it will!
REC: Who told you that?
Corp: The hardware vendor.

Fuckwits. Every last one of them. At this point I'd be thrilled to get a Citrix issue.