How many databases does YOUR organization have?
I know that databases are supposed to be repositories of important information, but they've morphed into huge piles of fetid trash.
Most databases are vile collections of (mostly) useless information arranged within carefully constructed "schema". It's called "schema" because the villains known as database administrators are "scheming" to prevent you from getting to any relevant information that may have made it past their defenses.
(Of course these database admins are only the second line of defense. The first line is the IT department which will ensure that you don't have the software, the computing power, or the login information necessary to access the database, without first signing away your life and securing approval from your VP's mother's dogs left testicle, but more of that in another post, later)
The most irritating of all databases are those will their own "work flows". Of course, they're there not to make work flow, but rather to impede the already glacial pace of work. They're called "work flows" because the database administrators want to demonstrate that they have a good grasp over the concept of "irony". Maybe you are not familiar with the concept of "work flows" because your backward company does not have a database. Fear not, o deprived one, I will enlighten you. A work flow is a series of steps that relevant information must stop at, be nitpicked over, changed unnecessarily and sometimes clubbed with a mallet and roasted over an open flame, till it is saddled with enough unnecessary accouterments to hide it's actual purpose, and is delayed long enough to not be timely anymore. Maybe you're thinking that "work flows" are unnecessary, but that's only because you are a lowlife cretin who does not understand that if work flows did not exist, you would never be able to ensure that any information is shrouded in templates, hampered by standards and is approved by people more in touch with the devil than you.
Don't get me wrong. I see the value of databases. It's not those mute tables that drive me up a wall, but the idiots that build them, encase them in rules and render them useless. Every moron who reads up on SQL code on the net wants to develop his own database because corporate databases wont cut the ice for his own specific microscopically unique needs, and so he runs off, downloads MySQL or Access and creates his own specific database and front end. Soon every company ends up with a gazillion little database, each of which contain one facet of information about their products or processes or people and none of which can share that information with the other. So just in case you are actually looking for information that will help you solve a problem, you have to first figure out whether or not that information exists, then figure out which database in exists in, and finally lay prostrate before the owner begging him to understand that your need is indeed a genuine one, before you can actually get your hands on the information.
Beset by similar woes last week, I devised a deliciously brilliant solution.
I'm going to start a database of databases. Every database owner must register in my database - without which his database will be wiped off the company servers. There's just one snag. I must lay prostrate before the gods in the IT department and convince them that my need is indeed genuine.
And our IT VP's mother dog is a bitch.