Slashdot Mirror
Dilbert Goes Flash, Readers Revolt
spagiola writes "The Dilbert.com website just got an extreme makeover. Gone is the old, rather clunky but perfectly functional, website, replaced by a Flash-heavy website that only Mordac the Preventer of Information Services could love. Users have been pretty unanimous in condemning the changes. Among the politer comments: 'Congrats. Vista is no more lonely at the top in the Competition For The Worst Upgrade In Computing Industry, this web site upgrade being a serious contender.' You have to register to leave comments, but many seem to have registered for the express purpose of panning the new design."
Comment removed based on user account deletion
Here's what I sent them earlier on when discovering that part of the site even does not support Linux:
And that's just one of my gripes. The new UI is clunky; the site is slow; ...
Linux user since early January 1992.
It's a freaking static cartoon! What possible asinine reason could there be to screw up such a simple concept? I saw this the other day and so, like Doonesbury, won't be visiting it any more due to their use of Flash.
We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
Well, yesterday and earlier today you couldn't see the comic w/o flash.
Thanks for pointing this out, I had just removed my cronjob to fetch-dilbert-and-set-as-wallpaper-script, probably need to rewrite it tough.
Actually, in a lot of places the office life is much the same. And, trust me, not only in the USA.
As a consultant, I can tell you that some of the projects I'm dragged into, the things I see, and the things I piece together, often make Dilbert look tame. At any rate, I see everything from Dilbert:
- Wally clones? Check. Armies of them.
One managed to work for 3 years to make a trivial module, that later someone else rewrote in 6 hours from scratch. The rewrite was also 40 times faster, when benchmarked on a large-ish data set. And that's just one of them. He also heavily obfuscated his code, with over half the techniques from "How To Write Unmaintainable Code." (If you can believe that variable names like Pete, Eve and Steve are anything else, I have a bridge in Sahara to sell. And that's just one of the dozens of sins of that code.)
I've also seen people whose day consists at least half, of doing the grand tour of all floors where they know someone, to find people to talk to. Probably the saddest case was one whose morning, from 9 to 12 consisted of making a list of what pizza each team member wants to order for noon. Now you're probably going, "wtf, that doesn't take 3 hours even for 100 people." Well, let me explain: not just going around and quickly noting what they want. He went and started a whole debate on the pros and contras of ordering a Calzone, or maybe a Quatro Stagioni this time. And, hey, did you see that today they have a special price for Pizza Margarita? With each and every person individually.
- Evil secretaries? Check. E.g., in one project they lost their best programmer, a contractor, when the secretary at the company that supplied him, cancelled his medical insurance just before his wife went into labour. Apparently, for no reason whatsoever, she just called the insurance company and said that he's getting a private insurance somewhere else. The guy understandably went "fuck you very much" and quit.
From what I hear, it was also quite the uphill battle to get her to do anything, including actually get the overtime paid that the client had already paid for.
Last I've heard, she got a promotion.
- Mordac The Preventer Of IT Services? Check. At times it feels like one in 3 guys in IT make it their goal in life to prevent everyone else from getting their job done.
A particular one, well, wasn't even consistent about what he wanted, except that it's the opposite of what you want. To one team and project it was "you're not getting queues unless they're all on the same queue manager", to another one in the same time interval it was "you're not getting queues unless they're on different queue managers". To one it was "you're not getting anything if you work with message timeouts, because it defeats the whole idea behind reliable messaging!", while to another one it was "you're not getting queues from me unless you set timeouts on the messages! I don't want you to fill the whole partition with old messages!" Etc.
One DBA argued that it's not his job to tune the production database.
And it doesn't seem to be entirely unheard of, that some company's internal IT department sets such outrageous prices for any service, that it would be cheaper to burn a large file on a CD and send it by _taxi_ to the other end of the country, than to use their network and their servers. In one place management was actually proud that their IT department is the most productive department in the company and makes the biggest profits. As if that's something positive, and not an undue burden on the other departments.
- Incompetent managers and incompetent management decisions? Oooer. I could fill a tome with those alone. But let's just say: some managers were keeping the above parasites employed. It's not even the biggest management sin I've seen, but it's enough to make me wonder, you know?
Etc, etc, etc.
Basically I'm talking a guess that all that changed there is that you got a new job sometime in the 90's, where that doesn't happen any more.
A polar bear is a cartesian bear after a coordinate transform.