Reading Comprehension

[billroper]

When someone reads something that I write and understands it, this is good.

When someone reads something that I write and doesn't understand it, this is correctable.

There are times when I question whether someone even bothered to read what I wrote, because if they did, they wouldn't have asked me to do the particular thing that they asked me to do, since I explained in great detail in what I wrote why it couldn't be done.

Well, it can be done, but you have to do this other thing first. And since I wasn't told to do the other thing, I kind of suspect that they didn't read what I wrote, that "other thing" requiring a certain level of planning before I can run off and do it.

So, is that cryptic enough? :)

Comments

[braider.livejournal.com]

Nope. I followed it perfectly.

They didn't bother reading what you wrote, and don't understand why you can't snap your fingers and do what they want now.

[sraun]

Is this one of those cases where "management" is a four-letter word?

[billroper]

If I told you, I'd have to kill you.

[chirosinger.livejournal.com]

Um.....So I don't get it.....Could you explain it to me again?.....

Clear as a bell.

[jalapenoman.livejournal.com]

It also helps if you put it in dollar and time terms, when it is business related.

"Can I get the software to do that?"
"No, that would take too long, and would be too cumbersome. The current method takes the designer maybe a half hour more to build the part."
"But can you get it to do that?"
"It will take 600 million dollars, and minimum ten years. Still want it?"
"Um, never mind."

(Actual conversation related to me by software engineer. I kid you not.)

[scs-11.livejournal.com]

Yes. Well, I mean, mostly. Not no, anyway. But you know what I mean.

Can you have it by Tuesday? In blue, please.