d bare bones

Ramon spam at thanks.no
Fri Sep 6 23:37:02 PDT 2013


On Saturday, 7 September 2013 at 05:35:04 UTC, H. S. Teoh wrote:
> I find that it's much more convincing for me to say "feature X 
> is
> broken, here's the code change to make it better", than to say 
> "feature
> X is broken, D sucks, you lazy bums better start working to fix 
> X or
> else I'm leaving".  It feels good to rant and get it off my 
> chest, but
> it feels even better to have my changes merged and feature X to 
> get
> fixed because of me.

My intention was and is not ranting, nor saying D sucks, nor
asking other to do work nor threatening. And this can found
proven in what I wrote.

Your personal attitude, which many others have, too, is one to be
respected and a necessary and productive one. Bot not the only
valid or constructive one.

Neither is there a need to decide; the options are not mutually
exclusive. As a seasoned programmer that I take you to be you
certainly can agree that leaning back and looking, incl. looking
critically at was has been done so far not only is not harmful
but it actually is positive and often even necessary. And you
will quite certainly also degree that a non trivial project will
need some planning and management.

Unlike what you seem to think, my point isn't hitting on D
(actually that's obviously nonsensical as I wrote just yesterday
or today that meanwhile I'm happily humming along with D).
But neither can it be a healthy attitude to ignore less pleasant
things or events. We should ask what's behind it and what we can
make better.

Simply fixing issues one at a time is not a solution per se but
rather one step in solving a problem albeit an important one.
Identifying reasons and patterns is also a step and often one
that considerably enhances the situation.

If today I'm a better devoloper than 20 years ago than not merely
by experience alone but by learning from mistakes and (in my case
an important lesson) by thinking extensively *before* I hack, by
learning the importance of good design and well proven principles
and, last but not least, by learning to recognize patterns in my
errors.

I try to be polite and respectful because I highly value the work
of WB, AA and others but I feel a suspicion that "shut up and
write code!" is not a solution but part of the problem in certain
regards.

But I respect your right to rant *g

A+ -R


More information about the D.gnu mailing list