[Scons-dev] Duplicate issue policy

[anatoly techtonik]

On Sun, Aug 10, 2014 at 6:09 PM, William Blevins <wblevins001 at gmail.com> wrote:
>> Knowing that you have only 15 minutes, you'd start to think differently.
>> First,
>> you'd try grepping on "class Copy" and "def Copy", then trying to choose
>> another
>> entrypoint, like knowing that it is somehow injected into Environment,
>> start with API docs for Environment.
>
>
> It would be nice if your argument didn't start with, you are idiot, but I
> understand your point.

I wish I could argument things differently, but I doubt there is an easy way to
change that. I'll have to relearn my way of thinking in English, because that's
just how a critical mind works. People want a critical approach, and then they
fire you, because it is too offensive. Maybe it is just that it is really
hard not to be a jerk while living a life of a looser. I guess the best
thing I can do without hijacking answer to a standardized "my life is a misery"
snippet, is to drop using "you" as a part of arguments. Would that help it
sound less personal?

>>  At the very end of your 15 minutes you start to think
>> "what can I do know so that the next person who approaches this issue
>> would
>> not have to start from scratch and get to the same position as I am?"
>
> Yeah, documentation is good.  Maybe intuitive design is a bigger concern.
> Perhaps we should consider naming files in a more self-documenting type of
> way.  Cross module dependencies, especially circular ones, make it harder.

I am not against that. But there is a limit of how much you can express in
application source code that has only two dimensions - files and lines. I place
my bet on tools that help to understand the complexity of a system by playing
with it and transforming its events into descriptive output that augments
limited human ability to process info.