Re: Why read CLC?
- From: "Pete Dashwood" <dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 11 Jun 2008 18:47:29 +1200
"Robert" <no@xxxxxx> wrote in message
news:4q7u44l0fsp7l15hpv1tmljvqc8009nip2@xxxxxxxxxx
On Tue, 10 Jun 2008 10:23:50 -0700 (PDT), "klshafer@xxxxxxx"
<klshafer@xxxxxxx> wrote:
On Jun 10, 9:19 am, "Pete Dashwood"
<dashw...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
<klsha...@xxxxxxx> wrote in message
[Pete]
[/Pete]
A blatant troll which I shall ignore...:-)
[Ken]
[/Ken]
I did not view it as a troll.
[Pete]
Given my stated preference for Agile development (which I have no
intention
of arguing here) it was a pretty blatant attempt on Robert's part to get
me
to respond...:-) It failed.
[/Pete]
Hmmmm... after reading your last statement, and re-reading Robert's
post on Constantine, I still cannot see it as a troll. But how am I to
know what is in Robert's heart?
So I shall just ask him, and hear what he has to say, if he deems it
worthy of a reply:
Robert, were your comments on Constantine a troll?
I saw it as blatant self-promotion, written by Constantine.
A troll posts inflamatory remarks intended to provoke an angry response. I
was trying to
provoke a reasoned response, not an angry one. Building a bridge (or not)
between 70s
software architecture, championed by you, and Agile, advocated by Pete,
seemed
appropriate to the discussion.
In my opinion, both Structured and Agile are somewhat flawed models for
three reasons:
1. Lack of substantiation. We are asked to take the author's word for
everything.
2. Influenced by computer capability/limitations.
3, Tied to style/fashion of one generation.
My favorite author on programming in the abstract is Steve McConnell in
Code Complete. He
substantiates claims with evidence and provides many citations. He sees
programming as a
craft rather than a work product. In other words, his audience is
programmers rather than
managers. He's not selling faster and cheaper, he is promoting quality. He
is agnostic as
to language and linguistic model -- object oriented versus verb oriented.
His theme is
that the biggest obstacle is the programmer's psychology and untrained
thinking, not
external forces such as users and managers. His approach is timeless and
self-sufficient.
It will never go out of date because human nature doesn't change.
http://www.practicalpc.co.uk/reviews/books/codecomplete2.htm
Robert, this is a simply excellent response and I withdraw my accusation
(which was made light-heartedly anyway... :-))
Good job. (I'm so impressed that I'll check out more on McConnell as soon as
I have some time.)
Thanks.
Pete.
--
"I used to write COBOL...now I can do anything."
.
- References:
- Re: Why read CLC?
- From: Robert
- Re: Why read CLC?
- From: klshafer@xxxxxxx
- Re: Why read CLC?
- From: Robert
- Re: Why read CLC?
- From: Pete Dashwood
- Re: Why read CLC?
- From: Robert
- Re: Why read CLC?
- From: Pete Dashwood
- Re: Why read CLC?
- From: klshafer@xxxxxxx
- Re: Why read CLC?
- From: Pete Dashwood
- Re: Why read CLC?
- From: klshafer@xxxxxxx
- Re: Why read CLC?
- From: Robert
- Re: Why read CLC?
- Prev by Date: Re: Why read CLC?
- Next by Date: Re: Why read CLC?
- Previous by thread: Re: Why read CLC?
- Next by thread: Re: Why read CLC?
- Index(es):
Relevant Pages
|