[petsc-dev] Pushing non-working code
Karl Rupp
rupp at mcs.anl.gov
Sun Feb 3 14:54:31 CST 2013
Hi,
> Since I'm on this list (less than a year) I regularly observed
> lots of resistance with respect to any changes of workflow. This
> can be either due to bad suggestions for improvement, or due to
> the emerge of an overly conservative development culture. I'm
> fine with the first option, but I fear the latter (not only
> PETSc-related).
>
>
> One more comment on an "overly conservative development culture". It is
> easy to see pushback on changes as
> unwarranted caution, whereas the other side sees it as preservation of
> desirable attributes. I think it would be just
> as easy to interpret the present changes as overly proscriptive, which
> are of course seen as improvements by the
> proposers.
I think we all know that there will - as you pointed out - always be two
sides of a medal. I'll silence myself with this
philosophically-yet-useless remark now and wait for Matt's data point :-)
Best regards,
Karli
More information about the petsc-dev
mailing list