Date: Wed, 12 May 1999 19:27:34 -0700 From: "David Schwartz" <davids@webmaster.com> To: "Chuck Robey" <chuckr@picnic.mat.net> Cc: <current@FreeBSD.ORG> Subject: RE: cvs commit: src/sys/pci pcisupport.c Message-ID: <000001be9ce8$291f3790$021d85d1@whenever.youwant.to> In-Reply-To: <Pine.BSF.4.10.9905122216130.401-100000@picnic.mat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Because if it's a day of coding, you should just do it. If it's a 3 > month project, you don't waste such time, and you should communicate it. > The time factor is judged by folks who code for a living, and maybe it's > a little high, but not too bad. I haven't seen this rule misapplied, > but it's possible some may think so; they are most likely mis-estimating > the scope of the work involved. Believe it or not, good ideas can even come from people who can't code at all, and the ideas are just as good. Slapping these people down just ensures they don't contribute in the future. Now if their ideas genuinely are bad, you are more than welcome to slap them down as much as you wish. If that means they don't contribute more bad ideas in the future, so much the better. Heck, it even may save you the idea of having to explain why the bad idea is, in fact, bad. But "if it's such a good idea, why don't you code it?" doesn't fall into any of these categories. It's one of those "that's what you think" type arguments that serves as an excuse to ignore the merits of the other side's case. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000001be9ce8$291f3790$021d85d1>