List Archive: gentoo-portage-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
Ciaran McCreesh wrote:
>On Wed, 5 Oct 2005 21:39:49 -0500 Brian Harring <email@example.com>
>| So bluntly, shut up and let those who you think are being retarded,
>| be retarded. Discussions on this list regarding those attempts
>| shouldn't be heckled unless you're contributing to those efforts (and
>| I truly mean *contributing*, not trying to punch holes in embryonic
>| efforts that are trying to get off the ground addressing the major
>| issues up front).
>Pfff. By contributing to the design by showing what *won't* work, I'm
>saving a heck of a lot of wasted man hours that will otherwise be spent
>writing a non-working solution.
>A contribution of code is worthless if the code is completely wrong, no
>matter how much effort was spent producing it.
>But then, we all know how this goes. When the code's 'done', it gets
>merged, and then you start claiming "If you had any issues with it you
>should have brought them up at the design stage. It's too late now!".
>So really, it's a no win situation. Point out gaping design flaws at the
>start and you're accused of shooting holes in things that don't exist
>yet. Point out gaping design flaws when it's first merged and you're
>accused of shooting holes in things upon which people have spent lots
>of time. Point out gaping design flaws after it goes live and you're
>told it's too late.
Then I suggest you file this e-mail away and when the time comes that
the code is to be merged and it sucks ( and by sucks I mean more than
"it doesn't meet Ciaran's software engineering standards" ) you can
waive the mail in everyone's face. No project, specs or not, is ever
written right the first time. At the very least someone can take his
code and improve on it in the future.
firstname.lastname@example.org mailing list