Note: I have since moved into a different industry, but this this still good food for thought, pun intended.
Sometimes the food is not so bad at the bottom of the food chain. Sure, it’s not champagne and escargot. But, hey, you need a Twinkie and bag of chips every now and again to satisfy.
I was thinking about this at work today, as the clamor in the office rose up. I work in an often hostile work environment. It occurred to me, on this particular day, that being a bottom feeder is not always a bad thing. Take for instance this newly redesigned database which holds critical information on the taxpayers in my State. The darn thing was full of bugs, as the previous version was written in-house by our IT guys. Nice guys and helpful sometimes. So, as the story goes there was not enough justification to purchase a hi-tech system, one that would allow us to link nationally to a database that would all but eliminate error. So, our IT guys, yes the same folks who wrote the first version, redesigned a new one. Hmmm.
That’s not all. What really causes heartburn is that there was no rollout of static data, we used live data since we had the chance to test multiple scenarios in a live setting. Hmmmm. I sure hope those of you who are Techies are clinching your jaw and are a bit queasy right this moment. Anyway, today, I found a bug or two (yes, in the newly redesigned version) and inquired of the powers that be on how to resolve it. (This is where the Twinkie comes in). In my ignorance of all things IT, I failed to realize how temperamental program writers can be. Turns out there is a certain “personality” written into each program and it behaves differently in alternate settings. As I continued on in my search of the mistake, I asked for help. My co-worker overheard and graciously chimed in. Turns out he has a degree in programming but is not currently working in that role. The writer took issue of the bugs that were discovered and revealed. My coworker took advantage of an opportunity to share some of his knowledge and a few of us were, just there. In the periphery. In my case, looking cute (smiles). I thought to myself at one point, “Oh, how I wish I knew what they were talking about. It would be so helpful to be able to solve some of these issues on my own. Or at least be able to speak some informed words into the issue”. Wait! Stop right there lady. There’s a saying that goes something like this: You can’t be good at everything. I was grateful this day, because although I found the error, my job ended at reporting it. Clearly I have no idea how to fix it. Don’t need to. Not my job. That is someone else’s specialty. Someone else’s talent.
I learned that sometimes ignorance can in fact be bliss. Well, bliss may be an overstatement. But, it can be convenient so say the least. By my not knowing anything about programming, I was able to avoid an office argument, hostile negotiations, hurt feelings, frustration, perspiration, palpitation and provocation. The only real residual harm done to me is that the explosion happened in my office, at my computer where the information was displayed on the screen. There was a bit of clean up from the “food fight”, which is okay with me. I had a Twinkie and a bag of chips in my desk when it was all done. So, I sat back and did what many bottom-feeders do. I ate to my heart’s content. Enjoyed every bite.