1 |
Ciaran McCreesh wrote: |
2 |
|
3 |
>On Wed, 5 Oct 2005 21:39:49 -0500 Brian Harring <ferringb@g.o> |
4 |
>wrote: |
5 |
>| So bluntly, shut up and let those who you think are being retarded, |
6 |
>| be retarded. Discussions on this list regarding those attempts |
7 |
>| shouldn't be heckled unless you're contributing to those efforts (and |
8 |
>| I truly mean *contributing*, not trying to punch holes in embryonic |
9 |
>| efforts that are trying to get off the ground addressing the major |
10 |
>| issues up front). |
11 |
> |
12 |
>Pfff. By contributing to the design by showing what *won't* work, I'm |
13 |
>saving a heck of a lot of wasted man hours that will otherwise be spent |
14 |
>writing a non-working solution. |
15 |
> |
16 |
>A contribution of code is worthless if the code is completely wrong, no |
17 |
>matter how much effort was spent producing it. |
18 |
> |
19 |
>But then, we all know how this goes. When the code's 'done', it gets |
20 |
>merged, and then you start claiming "If you had any issues with it you |
21 |
>should have brought them up at the design stage. It's too late now!". |
22 |
>So really, it's a no win situation. Point out gaping design flaws at the |
23 |
>start and you're accused of shooting holes in things that don't exist |
24 |
>yet. Point out gaping design flaws when it's first merged and you're |
25 |
>accused of shooting holes in things upon which people have spent lots |
26 |
>of time. Point out gaping design flaws after it goes live and you're |
27 |
>told it's too late. |
28 |
> |
29 |
> |
30 |
> |
31 |
Then I suggest you file this e-mail away and when the time comes that |
32 |
the code is to be merged and it sucks ( and by sucks I mean more than |
33 |
"it doesn't meet Ciaran's software engineering standards" ) you can |
34 |
waive the mail in everyone's face. No project, specs or not, is ever |
35 |
written right the first time. At the very least someone can take his |
36 |
code and improve on it in the future. |
37 |
-- |
38 |
gentoo-portage-dev@g.o mailing list |