- Sep 19, 2000
- 10,277
- 125
- 106
The Perl community is filled with a bunch of assholes. I asked a simple question "can this happen?".
Their response "OMG, you're so dumb, post your code",
so I post the code tell them exactly what I'm observing,
Their response "you should have newlines at the end of this function."
My response "No, the function automatically adds the newlines and besides, that is unrelated to the issue I'm having".
Their responses "OMG, you don't know that that is not the problem, your so dumb, I can't believe we ever stooped to your level to try an help you. You should post your logs"
I protested, I told them, "My logs are very long and they don't have a lot of useful information, please trust me when I say that this is what the output looks like."
Their response "Oh, we your so dumb, you didn't describe your situation well enough, you should post your logs."
My response, "Fine, here are the logs."
After that, they didn't say anything. Yes, it was a problem, no, they didn't know the solution to it... Gah, drives me nuts. They treat me like a 4 year old, insult me to no end, and in the end when I finally convince them that Yes, this is a possible problem, they don't say anything.
And yes, I still have the issue. The problem, I guess, is the fact that they generally don't work with very large perl projects, so they expect to have every single line of source code available to them to debug a problem (which simply isn't feasible". The functions weren't even all that abigously named, they were functions like "infoPrint", come one, why would you assume that does much more than printing. Yet they were bound and determined that was my problem (Even though I tried to explain to them that those were inserted by me to try and find the problem).
Their response "OMG, you're so dumb, post your code",
so I post the code tell them exactly what I'm observing,
Their response "you should have newlines at the end of this function."
My response "No, the function automatically adds the newlines and besides, that is unrelated to the issue I'm having".
Their responses "OMG, you don't know that that is not the problem, your so dumb, I can't believe we ever stooped to your level to try an help you. You should post your logs"
I protested, I told them, "My logs are very long and they don't have a lot of useful information, please trust me when I say that this is what the output looks like."
Their response "Oh, we your so dumb, you didn't describe your situation well enough, you should post your logs."
My response, "Fine, here are the logs."
After that, they didn't say anything. Yes, it was a problem, no, they didn't know the solution to it... Gah, drives me nuts. They treat me like a 4 year old, insult me to no end, and in the end when I finally convince them that Yes, this is a possible problem, they don't say anything.
And yes, I still have the issue. The problem, I guess, is the fact that they generally don't work with very large perl projects, so they expect to have every single line of source code available to them to debug a problem (which simply isn't feasible". The functions weren't even all that abigously named, they were functions like "infoPrint", come one, why would you assume that does much more than printing. Yet they were bound and determined that was my problem (Even though I tried to explain to them that those were inserted by me to try and find the problem).