Re: Why no SSCCEs?

Skip <a@xxxxxxxxx> wrote:
> Not much you can do about it, as they don't search for previous posts. Maybe
> the worst thing is that people actually read that massive code and try to
> point out (all) their bugs. It would be better when just a link was passed
> about SSCCEs, which often will cause them to find their bug, fix their code
> and live happily ever after.

Okay, I guess it's time to post my occasional plea asking people to not
be a jerk. So here it is.

That's the most convoluted piece of logic I've seen in some time.
Asking people to provide more information about their problem is fine.
Please, go ahead. It's your time that you would spend reading the post
and writing a helpful answer, and if you don't want to spend that time,
you have every right not to do so. It's certainly even decent of you to
*nicely* suggest that someone should provide more information.

Criticizing others for being helpful is just really screwed up. If new
programmers coming to the newsgroup get answers to their questions, then
the goals of the newsgroup are being achieved. The fundamental goal
here is not to get people to post an "SSCCE", but to help them with
problems they encounter in Java programming. If someone gets help but
doesn't post an "SSCCE", then that's great!

Before anyone starts whining, I should say this. It's true that going
through the exercise of creating a short piece of example code is very
helpful in finding problems. I've suggested it to people on several
occasions in the past, and Jon Skeet and I recommended it here well
before Andrew made up his pretentious acronym for it. I'm not trying to
convince anyone to stop making the recommendation.

It boils down to one basic question: are people who come here to ask
questions human beings, worthy of respect and dignity? I think so. And
I think the sentiment above treats them like dogs, to be trained into
acting exactly as others desire. I think it's sick.

PLEASE, PLEASE, PLEASE just consider a few ideas:

1. If someone's post is lacking information, and you'd be willing to
help them if they provide that information, then by all means ask for
it.

2. If someone's post just pisses you off, then ignore it.

3. Tell people that putting together a simple example would be helpful;
don't try to arrange for contrived consequences in order to force them
into it.

4. If you aren't here to help people or to engage in interesting
conversation, then please don't be here.

--
www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation
.