Skip to main content
Commonmark migration
Source Link

To add to the great answer that Cletus posted:

Sometimes a person has to do something less than ideal or stupid for reasons that are beyond their control (management, client demands, etc).

Or there can be some detail of the implementation that makes the "ideal" path not so ideal after all.

I've been in the former situation and it is already frustrating enough to have to do it The Wrong Way without someone telling you to abandon that route.

In those situations, I knew how to do it The Right Way. The reason is because The Right Way is simple and straightforward.

I have to ASK how to do it The Wrong Way because it's a crappier way to do it, and I never tried to do it the Wrong Way before.

It's a double-whammy of frustration to get non-answers that say "Don't do that, it's the WRONG WAY!". I was already frustrated that I had to resort to the wrong way, now I am even more frustrated because nobody will answer my question and they treat me like I'm a bit stupid (although most users are nice, some get rude).

I appreciate suggestions for better ways of doing things. However, these are usually good for comments, or for "asides" in an answer that actually addresses the question that was asked.

Good answer:

Well, I'd recommend doing X because it is really a better because of Y.

 

However, if for some reason you HAVE to do it this way, here's how: Z

Bad answer:

You're doing it wrong. You need to be doing X instead.

To add to the great answer that Cletus posted:

Sometimes a person has to do something less than ideal or stupid for reasons that are beyond their control (management, client demands, etc).

Or there can be some detail of the implementation that makes the "ideal" path not so ideal after all.

I've been in the former situation and it is already frustrating enough to have to do it The Wrong Way without someone telling you to abandon that route.

In those situations, I knew how to do it The Right Way. The reason is because The Right Way is simple and straightforward.

I have to ASK how to do it The Wrong Way because it's a crappier way to do it, and I never tried to do it the Wrong Way before.

It's a double-whammy of frustration to get non-answers that say "Don't do that, it's the WRONG WAY!". I was already frustrated that I had to resort to the wrong way, now I am even more frustrated because nobody will answer my question and they treat me like I'm a bit stupid (although most users are nice, some get rude).

I appreciate suggestions for better ways of doing things. However, these are usually good for comments, or for "asides" in an answer that actually addresses the question that was asked.

Good answer:

Well, I'd recommend doing X because it is really a better because of Y.

 

However, if for some reason you HAVE to do it this way, here's how: Z

Bad answer:

You're doing it wrong. You need to be doing X instead.

To add to the great answer that Cletus posted:

Sometimes a person has to do something less than ideal or stupid for reasons that are beyond their control (management, client demands, etc).

Or there can be some detail of the implementation that makes the "ideal" path not so ideal after all.

I've been in the former situation and it is already frustrating enough to have to do it The Wrong Way without someone telling you to abandon that route.

In those situations, I knew how to do it The Right Way. The reason is because The Right Way is simple and straightforward.

I have to ASK how to do it The Wrong Way because it's a crappier way to do it, and I never tried to do it the Wrong Way before.

It's a double-whammy of frustration to get non-answers that say "Don't do that, it's the WRONG WAY!". I was already frustrated that I had to resort to the wrong way, now I am even more frustrated because nobody will answer my question and they treat me like I'm a bit stupid (although most users are nice, some get rude).

I appreciate suggestions for better ways of doing things. However, these are usually good for comments, or for "asides" in an answer that actually addresses the question that was asked.

Good answer:

Well, I'd recommend doing X because it is really a better because of Y.

However, if for some reason you HAVE to do it this way, here's how: Z

Bad answer:

You're doing it wrong. You need to be doing X instead.

Source Link
TM.
  • 1.5k
  • 10
  • 15

To add to the great answer that Cletus posted:

Sometimes a person has to do something less than ideal or stupid for reasons that are beyond their control (management, client demands, etc).

Or there can be some detail of the implementation that makes the "ideal" path not so ideal after all.

I've been in the former situation and it is already frustrating enough to have to do it The Wrong Way without someone telling you to abandon that route.

In those situations, I knew how to do it The Right Way. The reason is because The Right Way is simple and straightforward.

I have to ASK how to do it The Wrong Way because it's a crappier way to do it, and I never tried to do it the Wrong Way before.

It's a double-whammy of frustration to get non-answers that say "Don't do that, it's the WRONG WAY!". I was already frustrated that I had to resort to the wrong way, now I am even more frustrated because nobody will answer my question and they treat me like I'm a bit stupid (although most users are nice, some get rude).

I appreciate suggestions for better ways of doing things. However, these are usually good for comments, or for "asides" in an answer that actually addresses the question that was asked.

Good answer:

Well, I'd recommend doing X because it is really a better because of Y.

However, if for some reason you HAVE to do it this way, here's how: Z

Bad answer:

You're doing it wrong. You need to be doing X instead.