PM,
I will be happy to discuss this with you after I finish the summary. I thought
that someone suggested that I write a summary but looking back I now see that
it was only a bit of undigested rhetoric. PM,Your criticism is only about
style. You have not actually formed any specific questions about issues in my
summary. If you cannot find anything that makes you wonder what I am getting
at in my summary then a picture and a specification isn't going to help.
Mike Tintner is willing to talk about a lot of substarantive issues but only on
his terms. When I tried to start a premised hypothetical conversation with him
on one issue that he had mentioned he completely blew it off because the
hypothesis started off with something that he could not accept. This showed me
that he was not willing to focus on particular issues other than to describe
those that would support his basic premises.
I just explained in my response to Mike Archibold how something I said could be
turned into a specific test. I did not go much further because I haven't
created and run the experiment yet, however, that could be seen as a
specification and a requirement. The only criticism that I think has any merit
so far was Steve's. What I am describing would probably be too slow. I had
thought that I had found a way around that problem, but now as I work further
on the summary the complexity of what I am describing has returned. I am truly
sorry that you others are unable to benefit from what I am writing. However,
there is no good reason to become annoyed about that. If you have any
questions about what I am writing I will be happy to discuss them with you
after I finish the summary. Jim Bromer
From: [email protected]
Jim, To reiterate for the Nth time, software developers communicate with one
anotherand themselves via requirements and specifications, not synopses.
Having target state diagrams (UML or other) with static and dynamic views will
help people understand what is going on in your head. Of course you understand
it. But if you want assistance, or you are interested any at all in having
other people understand it. You should consider creating requirements,
specifications, and diagrams. Text summaries are only for philosphers, not
software developers. Just my opinion.~PM
-------------------------------------------
AGI
Archives: https://www.listbox.com/member/archive/303/=now
RSS Feed: https://www.listbox.com/member/archive/rss/303/21088071-f452e424
Modify Your Subscription:
https://www.listbox.com/member/?member_id=21088071&id_secret=21088071-58d57657
Powered by Listbox: http://www.listbox.com
