Re: One-liners
- From: "MikeD" <nobody@xxxxxxxxxxx>
- Date: Sun, 1 Apr 2007 21:30:01 -0400
"Rick Rothstein (MVP - VB)" <rickNOSPAMnews@xxxxxxxxxxxxxxxxx> wrote in
message news:uajLzdHdHHA.4032@xxxxxxxxxxxxxxxxxxxxxxx
Okay, I've given a lot of thought to the issue of one-liners and have
decided not to use, develop or post them any more. It seems that some
people have been using them directly in their own code, without
understanding how they work and getting in trouble at work when doing so.
I even got feedback that one person was fired for doing this. Sorry, but I
won't be responsible for that happening again. So, no more one-liners... I
hope those of you who used to look forward to them won't be too put out by
my decision.
Rick,
While I understand you not wanting to be (or even partially feel)
responsible for unfortunate circumstances....I think your decision is a bit
extreme. Now, I'm not big on one-liners. I don't like them. The reason is
because I don't think they're "clear and concise" and therefore not "good"
code (the apparent reason you're choosing not to post them anymore).
BUT.....I was always intrigued by your one-liners, even if I didn't agree
with them.
The way I see it is that ALL code posted here is for EXAMPLE purposes only.
You, me, or anyone else who posts code is NOT responsible IN ANY WAY for
that code being used in "production code". If a person chooses to use posted
code "as is", that's his/her decision. They should know any coding standards
that are required and modify the code to meet those standards. If they don't
understand the code, then it's their responsibility to dissect it so that
they can understand it....and choose to use it "as is" or modify it to make
it more understandable. If they don't do that, it's their problem. It's not
your fault, or anyone else's, that they didn't do that. Now, I would feel
extremely bad if someone used any code that I posted "as is" and got fired
for it. But I would NOT feel responsible for him/her getting fired.
I hope you reconsider. Remember, I don't like one-liners and yet I'm still
asking you to reconsider. <g> Perhaps you can add a disclaimer, or
something along the lines of recommending the code not be used "as is" (e.g.
that it's for example purposes only). Perhaps that's something we all should
do. It's kinda sad, but perhaps that's reality. With more and more frivolous
lawsuits being filed every day, I suppose those of us that post code can't
be too careful to protect ourselves (although I find it really hard to
believe we could be held liable for any code we post).
--
Mike
Microsoft MVP Visual Basic
.
- Follow-Ups:
- Re: One-liners
- From: Michael C
- Re: One-liners
- References:
- One-liners
- From: Rick Rothstein \(MVP - VB\)
- One-liners
- Prev by Date: Re: Ta Dah! Good-bye guys!
- Next by Date: Re: Ta Dah! Good-bye guys!
- Previous by thread: Re: One-liners
- Next by thread: Re: One-liners
- Index(es):
Relevant Pages
|
