Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Review of Steve McConnell's AFTER THE GOLD RUSH

16 views
Skip to first unread message

Al Dunbar

unread,
Nov 28, 2000, 3:00:00 AM11/28/00
to
Is it just me, or does this post somehow fail to give any real information
about the actual book it purports to review? Is the book as much about
"bricolage" as this article is?

All I can tell is that Mr Spinoza (?) does not like the book. I cannot tell
from his rant exactly why this is the case, or why I should share his
opinion.

/Al

<spino...@my-deja.com> wrote in message
news:901k5k$pm7$1...@nnrp1.deja.com...
> Steve McConnell, AFTER THE GOLD RUSH: Creating a True Profession of
> Software Engineering. Redmond, WAS: Microsoft Press 2000.
>
> Since the 1970s, books like After the Gold Rush have been frequent and
> unchanging. They notice that most software is developed using
> techniques that are apparently what the French call bricolage, on the
> face of it rules of thumb rather than the more scientific principles of
> traditional engineering. They then urge greater maturity upon software
> developers in an hortatory fashion.
>
> What we need to realize is that software engineering is a science of
> man. Its mistake is to transfer the objectification of nature to human
> behavior, thereby becoming, in Nietzche's sense, a form of truth/power
> and a tool for domination.
>
> There is nothing wrong with Nietzchean truth/power and I don't mean to
> reject Nietzche's epistomological discoveries. But there is a real
> problem with truth/power that denies its power component.
>
> C. S. Lewis pointed out that Renaissance science was not so much a tool
> for the disinterested domination of nature as a magician's tool for the
> control of people, and shortly after Lewis, Thomas Kuhn confirmed this
> from within the scientific establishment. Francis Bacon was not only a
> disinterested scientist but also heavily involved with the politics of
> his era and the desire of the Tudor magnates to bring England's people
> under centralized control.
>
> Nonetheless the software engineers believe, by reducing what they
> regard as the bricolage of the traditional computer programmer and by
> increasing the use of empirical tools and visual aids, software
> engineering will then succeed in the manner of traditional
> engineering. Power, they believe, will realize truth, as long as the
> subordinate software engineers and "coders" can be persuaded of the
> truth and kept ignorant of the power.
>
> The rhetoric presents a "new, enlightened, scientific" way of
> developing software and it is opposed to the "old" way of doing
> things. The problem with this is that if you know software history in
> any detail, you discover that a number of different types
> of "bricolage" were used, varying (much like software engineering) from
> bad ideas to good ideas, including the use of high level languages, and
> any number of efficient algorithms.
>
> Admiral Hopper, for example, discovered in the 1940s that the computer
> itself could be used to develop software. This seminal idea was of
> course recognized, but not at the time Adm. Hopper reported her
> discovery.
>
> At the time, many people regarded her discovery as bricolage and as
> unworthy of much note, insofar as the discovery was noted at all. The
> reception of an innovation as "engineering" or "bricolage" depends on
> social networks constructed in detail by power.
>
> In a similar fashion, the "structured programming" guru Edward Yourdon
> gave as an example of the bad, old, bricolage an unnamed programmer who
> he said had said "Go tos are bad." The problem was that what Yourdon
> was reporting was a letter from Prof. Edsger Dijkstra, now at the Univ
> of Texas, to the Communications of the ACM in 1968 that triggered the
> structured revolution (which Yourdon privatized and exploited.) Here,
> Yourdon neatly reversed what one would expect to be the truth/power
> relation between himself, and Prof. Dijkstra because Yourdon
> capitalized the idea whereas Dijkstra preferred a less powerful
> academic position.
>
> Today, bricolage has continued to produce success. Linus Torvaldys'
> bricolage proved that even operating systems could be fabricated by
> individuals with no power relations between each other.
>
> The praxis of actual computer programmers varies widely. However,
> software engineering mavens think it's all bad praxis which, they
> claim, should be more controllable by "normal people", defined in
> America as management, and management-oriented.
>
> "Normal" people seem to be those who more or less willingly adapt to a
> life structured in detail by power. To take one example, the "normal"
> software developer accepts without discussion the capillary power
> relation known as "going to work", involving so often exhausting and
> meaningless daily drives from point A to point B in order to satisfy
> the undiscussed proposition that (a) the corporation needs to watch him
> work, because (b) absent this Panopticon, the employee would
> immediately assert the converse power relation known as goofing off.
> Of course, this misses the very idea, absent as it is from a network of
> power, that one might like to work.
>
> Software engineering assumes two propositions, one of which is true,
> and the other, quite false. The true proposition is that developing
> large software systems is hard. The false proposition is that people
> must be forced to work at this task and that there is no personal,
> subjective, joy of creation.
>
> For example, Steve presents as a sort of model of software development
> in the beginning of the book the building of the Pyramids. He does not
> question the value to society of sarcophagi exalting the vanity of
> Pharaoh. Nor does Steve question the value to society of software
> sarcophagi (eaters of the dead) erected as monuments to CEO vanity.
> This is not to downplay the necessity of large scale software. But it
> is to show that perhaps Pharaoh's slaves did not develop, in the up and
> coming Yankee fashion, clever tools to do the job not so much of a lack
> of knowledge, as a lack of power, and a learned unwillingness to get in
> trouble with the overseers.
>
> Early programmers developed many techniques that newbies have yet to
> learn properly. Programmers were only accidentally members of a guild,
> and this "priesthood" steadily expanded. New monks may have been
> occasionally whacked upside the head for their own good, and users
> demanding the logical equivalent of cold fusion have occasionally been
> sassed, even when they were CEOs: the disruptive backtalk, not the
> bricolage, was the real problem.
>
> Instead of a "priesthood", there was that rarity, the career open to
> talents. Programming has long represented "some way outa this place"
> to people from broken homes, minorities and women. But after years of
> struggle, these folks find social relations unchanged, and they view
> top-down rhetoric about "software engineering" with suspicion and
> hostility. But because they don't have the tools to organize these
> thoughts, this becomes a populist programming anti-intellectualism
> which is part of the problem set, and is marshaled by management to
> resist Steve's goals.
>
> It is simply not likely that even a licensed software engineer will be
> able to hold up a development project in the way that Steve describes,
> by refusing to sign off. Steve takes as frozen and given traditional
> professional/organization power relationships, including that of the
> doctor to his hospital or HMO and that of the lawyer to the megafirm,
> and Steve commits a naturalistic fallacy, for for the same reasons
> programmers cannot seem to professionalize, doctors and lawyers are
> being steadily reduced in power by the same forces programmers face:
> those of cost accounting and naked authority.
>
> The programmer will always represent a scandal: the scandal he
> represent is so unspeakable that it only appears in old myths including
> the Nibelunglied with its account of the relationship of systems (the
> laboring gods who built the palace of the new gods and who wanted to be
> paid.) To be second nature, the administered world has to break this
> nexus and it has and will use all methods up to and including
> liquidation of programmers as a class; for example, researchers have
> found that many "programmers" spend their days doing anything but
> writing code.
>
> Steve does not have much respect for computer science which to me is
> closer to original programming praxis and he feels that enrollments are
> declining in CS because the so-called "market" of prospective students
> shrewdly perceive writing compilers and learning graph theory as
> valueless. This ignores the fact that this market by definition
> doesn't know what it needs, and it also ignores the fact that many
> software products are indeed at some level formal languages. Their use
> demands at a mininum an appreciation for what Dijkstra has described as
> the cruelty of symbolic manipulation. Their fabrication does indeed
> involve at various times the writing of compilers and the
> understanding, at the level of theory, the idea of graphs.
>
> The "software engineer" may very well go to work believing that
> computer languages from SQL to various fourth and fifth generation
> proprietary languages are now so powerful that they understand, in the
> manner of human languages, subtle shades of meaning and all stupid
> errors. But these folks will also, courtesy of lack of humanistic
> culture, fail to grasp just how vast human capability for
> nondenumerably large shifts in meaning can be.
>
> They will be, in other words, modern barbarians of an administered
> world that will not see what it is about, and that will regard human
> creations blasphemously as a second form of nature, more controllable
> by empirical techniques than by logical analysis. What will result,
> and what has already resulted, is more domination of man by man, and
> more "I'm a software engineer, and you're a mere coder." Steve, after
> Code Complete, I expect more from you.
>
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.

spino...@my-deja.com

unread,
Nov 28, 2000, 7:55:18 PM11/28/00
to

Jason Stokes

unread,
Nov 29, 2000, 1:51:58 AM11/29/00
to
On Tue, 28 Nov 2000 20:56:07 -0700, Al Dunbar <Al_D...@HoTMaiL.com> wrote:

>Is it just me, or does this post somehow fail to give any real information
>about the actual book it purports to review? Is the book as much about
>"bricolage" as this article is?
>
>All I can tell is that Mr Spinoza (?) does not like the book. I cannot tell
>from his rant exactly why this is the case, or why I should share his
>opinion.

It's a fairly standard poststructuralist English Lit composition with nods
towards Foucault, Nietche etc. Particularly incongruous in a book about
software engineering, methinks.

Patrick Logan

unread,
Nov 29, 2000, 3:00:00 AM11/29/00
to

"Jason Stokes" <js...@bluedog.apana.org.au> wrote in message
news:slrn929a1...@valis.local...

Which illustrates his point, I fear.

--
Patrick Logan
mailto:patric...@home.com


Jason Stokes

unread,
Nov 29, 2000, 3:00:00 AM11/29/00
to
On Wed, 29 Nov 2000 18:05:21 GMT, Patrick Logan <patric...@home.com>
wrote:

>"Jason Stokes" <js...@bluedog.apana.org.au> wrote in message
>news:slrn929a1...@valis.local...

>Which illustrates his point, I fear.

Hmmm?

I can't see why a software engineering book would want to address the kinds
of things he's talking about in his review, or have any relevance to such
issues. A programming book is about on the same level as a book on
carpentry as far as social commentary is concerned.

spino...@my-deja.com

unread,
Nov 29, 2000, 3:00:00 AM11/29/00
to
In article <t28vin8...@corp.supernews.com>,

"Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
> Is it just me, or does this post somehow fail to give any real
information
> about the actual book it purports to review? Is the book as much about
> "bricolage" as this article is?

It's just you, Al. The review is not meant to be a "consumer guide",
or ersatz for reading the book. For that, plenty of information is
available on www.amazon.com and www.barnesandnoble.com.

The review is instead critique that airs views about "software
engineering" that seldom see print.

Sorry you did not get value from the review, but if you do not share my
disquiet about the ways in which some software engineers at one and the
same time use and diss academic computer science, and programming
bricolage, then the review wasn't meant for you.

>
> All I can tell is that Mr Spinoza (?) does not like the book. I
cannot tell
> from his rant exactly why this is the case, or why I should share his
> opinion.
>

Actually, I "liked" the book in the sense that it held my attention,
and I really liked Steve McConnell's book Code Complete. I also have
personal admiration for Steverino, who I met briefly.

spino...@my-deja.com

unread,
Nov 29, 2000, 3:00:00 AM11/29/00
to
In article <slrn929a1...@valis.local>,

Why? Software engineering is not pure science and makes a partly
logical and partly rhetorical case for its methods. Its science
happens to be pretty good.

The problem is that the rhetoric seems to rely on acceptance of power
relations that are not guaranteed to produce success, and a fair
outcome for all stakeholders.

Part of the reasons organizations "buy in" to software engineering
methodology and then in a striking number of cases fail to realize the
promised savings, is precisely because the engineers haven't read
Foucault and Nietzche and do not view software engineering as BOTH
applied science and applied force.

Because they are simply unaware that they are on the receiving end of
power, rather than their traditional, comfortable and protected
position on the delivery end, they do not know how to pushback
appropriately when the methods are misapplied.

This results in an organizational cynicism in which it is pronounced
that the methods work, and that the diagrams and methodologies
correspond to the code, while the passive-aggressive engineers more or
less sullenly proceed to try to implement the system, with its
necessary aporias (gaps) resulting from the superficiality of the
design.

spino...@my-deja.com

unread,
Nov 29, 2000, 3:00:00 AM11/29/00
to
In article <slrn92aij...@valis.local>,

js...@bluedog.apana.org.au (Jason Stokes) wrote:
> On Wed, 29 Nov 2000 18:05:21 GMT, Patrick Logan
<patric...@home.com>
> wrote:
>
> >"Jason Stokes" <js...@bluedog.apana.org.au> wrote in message
> >news:slrn929a1...@valis.local...
> >Which illustrates his point, I fear.
>
> Hmmm?
>
> I can't see why a software engineering book would want to address the
kinds
> of things he's talking about in his review, or have any relevance to
such
> issues. A programming book is about on the same level as a book on
> carpentry as far as social commentary is concerned.

That's the problem in a nutshell. The carpenter constructing a house
for a wealthy software engineer that his family cannot afford would be
well advised to preface his book on carpentry with reflections on the
justice of this situation. He'd also be well advised to work as hard
as possible to place on display, for future generations, that his
dignity survived a society in which homes are ever more lavish, yet
ever more unaffordable for vast segments of the population.

Even if we accept the ground rules of our society, which uses
inequality to motivate us to go to work, an intelligent manager would
do well NOT to naively present software engineering as just another
technology. He'd be sensitive to the feelings of his programmers, even
though he might, given the ground rules, proceed to downsize and in
general stick it to them anyway.

For it is very true that there are many programmers who THINK their
bricolage is the greatest thing since sliced bread, and who are quite
wrong. This truth happens to be logically consistent with the fact
that there are others (Andy Herztfeld of Apple comes to mind) who
indeed are world class geniuses but who nonetheless shafted by the
rhetoric of "structure" and "software engineering" anyway. In a 1986
interview, Andy relates how after developing the code for the
Macintosh, he nonetheless got a bad performance review that devil a
doubt used the management rhetoric of "structure" and "being a team
member."

Software engineering is excessively top down in that it "freezes" the
goals of the project even when the developers realize that these goals
need to be changed. Another Apple example is Hypercard: in the early
days of the Mac, it was difficult to develop even simple graphic
applications because they were an enormous hack in C or Basic. Bill
Atkinson wanted to make an end-run around this problem by developing a
sort of generalized graphical interface based on a "card" metaphor. He
had to work very hard on tasks set to him by Sculley until he received
the go-ahead as a "reward."

Actually solving a problem that underlay the problem as it was
management defined was treated by John Sculley as a trip to Cancun, a
reward, and a detour and frolic...when in fact Hypercard saved the
Mac. I fear that the software engineering approach, by its emphasis on
the "user" (ill-defined as only one stakeholder) and
his "requirements", does tend to prevent what used to be known within
IBM as pushback: bottom up critique and suggestions, including
Hypercard.

Please keep in mind that I am a software developer and not an English
teacher, although I have taught logic and critical thinking as well as
Visual Basic. I'm not bringing Foucault up to be pretentious, although
I can be quite pretentious when I want to be :-).

Jason Che-han Yip

unread,
Nov 29, 2000, 3:00:00 AM11/29/00
to
<spino...@my-deja.com> wrote in message
news:903jdm$bqq$1...@nnrp1.deja.com...
> In article <slrn929a1...@valis.local>,

<snip>

> The problem is that the rhetoric seems to rely on acceptance of power
> relations that are not guaranteed to produce success, and a fair
> outcome for all stakeholders.
>
> Part of the reasons organizations "buy in" to software engineering
> methodology and then in a striking number of cases fail to realize the
> promised savings, is precisely because the engineers haven't read
> Foucault and Nietzche and do not view software engineering as BOTH
> applied science and applied force.

I have neither read Foucault or Nietzche so perhaps that's why I don't know
what you mean by applied force. I'm guessing that you're saying that
humanistic issues can and will cause approaches to fail.

Greg Menke

unread,
Nov 29, 2000, 3:00:00 AM11/29/00
to

>
> Well, something has to freeze the goals of the project, if only to
> allow it to be completed. In my experience, it is usually the
> marketing department which does the goalpost moving function which you
> seem to require.
>
> What do you propose to fulfill the function of meeting the ever moving
> goal?
>
> In your scheme, how will projects be delivered as "completed"?


I think he's referring more to the slavish adherence to method over
substance; ie spending time in endless meetings talking about
"process" and "living documents" rather than digging into the real,
contradictory and ill-defined requirements a system must meet.

Getting the real requirements amounts to doing an old-fashioned
systems analysis on the existing system, learning what it does and
how, then identifying what the users need (in contrast to what the
users say they need). If the user cannot/will not define their goals
& requirements then you can't build a sucessful system no matter how
much time/money you spend. You may well build some things which do
work, but I imagine you'll end up in a never-ending development
process.

To be sure you have to shoot the analysts and start coding at some
point, but there is a difference between trying to avoid gratuitous
changes in requirements & spec and an arbitrary halt to all
consideration of change. The latter is a recipe for building a system
that doesn't meet user requirements even IF it actually gets
delivered. The former is how you adapt to a complicated and
incompletely understood problem- its imperfect, demanding, expensive
and not very predictable, but its what you have to do. You can either
have an expensive system you do once or a REALLY expensive one you
have to redo a quantity of times.

The trouble with many Software Engineering principles and
methodologies is they don't concentrate on doing the time-consuming,
difficult and error-prone process of getting the system requirements
straightened out- instead relying on "well defined procedures" which
are easy to specify, but don't help much when trying to understand
what a system needs to accomplish- or more importantly, coaxing a
non-technical project lead to devote his/her resources to spending
time with the users.

I've been developing systems of varying complexity since 1990 and have
yet to hear of a software engineering methodology which improves
significantly on the basic principle of studying what the user needs,
organizing it, adapting to change and implementing- usually in
combination. UML isn't much more than a notational change to the
entity/relationship/"flowcharting"/whatever we did a decade ago. The
CASE tools have marginally improved since, but not markedly. But
thats only my take on it... no doubt I'm part of the problem.

Frankly, I figure the SEI rating stuff has a half-life of about 4
years, its got 5 or 6 more before it falls into the dustbin of
antiquity. But, its in good company with TQM and all the other
philosophies which aren't dealing with the hard problems.

Gregm

spino...@my-deja.com

unread,
Nov 30, 2000, 12:31:40 AM11/30/00
to
In article <904d7k$1ep4$1...@nserve1.acs.ucalgary.ca>,

"Jason Che-han Yip" <j.c...@computer.org> wrote:
> <spino...@my-deja.com> wrote in message

Foucault and Nietzche both showed how truth and power are linked and
are two sides of the same coin.

An example would be the plight of the "computer nerd" who makes a
presentation. People tend to mistrust him (his gender is typically
male) and dismiss his concerns as marginal to the "bottom line" or
the "main issues."

In ordinary biztalk it is said that the nerd needs to
learn "communications skills." While mechanical communications skills
such as how to make a presentation are of course valuable what is often
meant is not that the message was "communicated" poorly: it is a
failure to understand the message, or disagreement with its import.

And, following Foucault and Nietzche, we'd have to say that the
audience in the presentation inherits social attitudes. Computer nerds
have low status in American culture, therefore the audience tends to
discount what they have to say...whereas he who adopts the pose of
management gains truth through at least the appearance of power. Power
makes truth.

Patrick Logan

unread,
Nov 30, 2000, 1:47:15 AM11/30/00
to

"Giles Todd" <g...@at-dot.org> wrote in message
news:4reb2tog59deslfpn...@4ax.com...

> On Wed, 29 Nov 2000 19:15:43 GMT, spino...@my-deja.com wrote:
>
> > Software engineering is excessively top down in that it "freezes" the
> > goals of the project even when the developers realize that these goals
> > need to be changed.
>
> Well, something has to freeze the goals of the project, if only to
> allow it to be completed. In my experience, it is usually the
> marketing department which does the goalpost moving function which you
> seem to require.
>
> What do you propose to fulfill the function of meeting the ever moving
> goal?
>
> In your scheme, how will projects be delivered as "completed"?

The moving goal post is a reality that will not go away, ever. "Completed"
will
never be defined solely by the developer, having been handed a requirements
specification.

Software development has to come to terms with change *as* development
proceeds. (Top down is not the answer.)

Tom J

unread,
Nov 30, 2000, 3:00:00 AM11/30/00
to
Hi. "Software Engineering" does not require that requirements be frozen up
front. I think that DOD STD 2167A did so.
"Software Engineering" is a huge field big enough to include any
measured project management approach, including
measured iterative approaches.

Be careful of your examples of genius. I didn't buy an Apple, I bought an
Amiga. Now that's genius. Pre-emptive multitasking 12 or 13 years before
Apple on a $550 box.


--
Tom J.; tej at world.std.com Massachusetts USA; MSCS; Systems Programmer
Dist. Real-Time Data Acquisition S/W for Science and Eng. under POSIX,
C, C++, X, Motif, Graphics, Audio http://world.std.com/~tej

Al Dunbar

unread,
Nov 30, 2000, 3:00:00 AM11/30/00
to

<spino...@my-deja.com> wrote in message
news:903ivs$bde$1...@nnrp1.deja.com...

> In article <t28vin8...@corp.supernews.com>,
> "Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
> > Is it just me, or does this post somehow fail to give any real
> information
> > about the actual book it purports to review? Is the book as much about
> > "bricolage" as this article is?
>
> It's just you, Al. The review is not meant to be a "consumer guide",
> or ersatz for reading the book. For that, plenty of information is
> available on www.amazon.com and www.barnesandnoble.com.

I find it odd that you say that it is just me. The initial replies of Jason
Stokes and Patrick Logan seemed to me to be somewhat in agreement with my
comments. The fact that the thread has devolved into a discussion, however
valuable, that nonetheless has no bearing on the book also tends to support
my view.

I am well aware of the other sources of book review information that you
mention. Since I have never seen a negative review at a site that wants to
sell me a book, I generally find the newsgroups to provide more reliable
criticism. Just not in this case.

> The review is instead critique that airs views about "software
> engineering" that seldom see print.

It was fairly obvious that your post was, as you say, not a review of the
book but a critique that airs views that may or may not have had any
relationship whatsoever with the content of the book itself. Now, I am not
saying that I disagree with the content of your "review". Actually, I did
find it difficult to discern your actual views from your particular writing
style, which I think drew other comments as well. But that is neither here
nor there. Why did you call it a review of one specific book when it was in
fact an invective against what you disagree with about writers of such books
in general?

> Sorry you did not get value from the review, but if you do not share my
> disquiet about the ways in which some software engineers at one and the
> same time use and diss academic computer science, and programming
> bricolage, then the review wasn't meant for you.

I may indeed share your disquiet; I just have difficulty understanding what
you are getting at. Now, maybe that *is* just me.


/Al

spino...@my-deja.com

unread,
Nov 30, 2000, 3:00:00 AM11/30/00
to
In article <t2cuv33...@corp.supernews.com>,

"Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
>
> <spino...@my-deja.com> wrote in message
> news:903ivs$bde$1...@nnrp1.deja.com...
> > In article <t28vin8...@corp.supernews.com>,
> > "Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
> > > Is it just me, or does this post somehow fail to give any real
> > information
> > > about the actual book it purports to review? Is the book as much
about
> > > "bricolage" as this article is?
> >
> > It's just you, Al. The review is not meant to be a "consumer
guide",
> > or ersatz for reading the book. For that, plenty of information is
> > available on www.amazon.com and www.barnesandnoble.com.
>
> I find it odd that you say that it is just me. The initial replies of
Jason
> Stokes and Patrick Logan seemed to me to be somewhat in agreement
with my
> comments. The fact that the thread has devolved into a discussion,
however
> valuable, that nonetheless has no bearing on the book also tends to
support
> my view.
>
That's great Al. But it's just you, and thousands of other developers
who share your assumptions and your world-view.

Look, mate, I am well aware that MOST developers in our culture would
feel that my concerns are not relevant to software engineering is in my
view part of the problem set. I am well aware that the very idea that
literature, or Foucault, has any relevance to software engineering is
strange, indeed offensive to developers who believe that software
engineering is Science.

I am trying to explain the vague unease that many of these developers
nonetheless feel at the fact that parts of software engineering seem
more concerned with dominance and control than with Science. I am
trying to account for the programmers who left early structured
walkthroughs in tears because their world view turned out to be
inconsistent with the realities of capillary power.

> I am well aware of the other sources of book review information that
you
> mention. Since I have never seen a negative review at a site that
wants to
> sell me a book, I generally find the newsgroups to provide more
reliable
> criticism. Just not in this case.
>

Amazon posts negative reviews. It's posted my review of Steve
McConnell as of today. For positive and negative customer reviews
check Customer Comments. You are sure to find people who share your
concerns rather than mine, and who give unbiased information.

> > The review is instead critique that airs views about "software
> > engineering" that seldom see print.
>
> It was fairly obvious that your post was, as you say, not a review of
the
> book but a critique that airs views that may or may not have had any
> relationship whatsoever with the content of the book itself. Now, I
am not
> saying that I disagree with the content of your "review". Actually, I
did
> find it difficult to discern your actual views from your particular
writing
> style, which I think drew other comments as well. But that is neither
here
> nor there. Why did you call it a review of one specific book when it
was in
> fact an invective against what you disagree with about writers of
such books
> in general?
>

Again: issues of writing style are part of the problem set. Some
software engineering, in an honest attempt to visualize complexity,
oversimplifies complexity that ultimately can only be expressed by a
text. For example, many developers of database systems place, on the
walls of their cubicles, elegant maps of the key relationships of
whatever data base they have been developing and managers and many
developers believe that this artwork shows that the project is under
control.

The problem is that as most database systems evolve over time, these
charts, difficult to produce even using excellent tools such as Visio,
become perniciously out of date. The devil is in the details, for
their express purpose of serving as an encyclopediac quick reference
simply is not met in critical cases.

This is overall a freeze-frame approach to technical reality...which is
influenced not so much by scientific or technical considerations as by
our culture, which is ahistorical and present-oriented. For the same
CULTURAL reason developers flock to blockbuster movies with freeze-
frame "happy endings" they seek to freeze software in visuals despite
the known fact that requirements change.

The reality is that of the program text (as Derrida said, there is
nothing but the text.) This is partly to say, like the old-fashioned
programmer, that the code is the documentation and as such it will be
an unattractive conclusion both to me, and to the software engineers
and architects. But an Open Source approach to code can make this
reality far more transparent than it is. Most business systems that
affect our lives are protected by a wall of documents, made with the
best of intentions, that simply are not known to correspond to the
working code.

However, this has a result that will be frightening to American
business. To use Open Source for critical business systems is to open
your books to public oversight and control.

Most CEOs are honest according to current standards, and they don't
want their accounting software to violate generally accepted accounting
systems, and businesses no longer run their own payroll in order to
ensure their employees aren't screwed by private payroll software.

Nonetheless, there is a competitive advantage in running software that
accidentally or purposely ignores laws the business does not like.
Plausible deniability (where the CEO, and even the CIO does not KNOW
that the software is systematically and unfairly giving them an
advantage) kicks in, and the corporation enjoys advantages in closed
source that would be lost in open source. For example, IBM for years
monkeyed with its pension software for years, making almost
incomprehensible changes that systematically screwed its retirees.

This message takes as many words as it takes. Part of the problem set
is the brutalization of writing style found in design documents where
simplification for its own sake is accounted a virtue.

As to "invective." Because software engineering is as much about power
as it is about truth, it has treated critique not thoughtfully but with
a certain amount of brutality. For example, computer scientist Edsger
Dijkstra gained a reputation in the 1970s as a bad boy for defining
software engineering as "programming, for people who can't program."

There are all sorts of programmers, and some of them have risen from
the working class and themselves worked very hard to learn their
trade. Software engineering tends to diss them in a uniform way as
trolls. Of course, for the last 40 years, the trolls have had the
last laff in the job market, for like Kipling's British soldier:

It's Tommy this, and Tommy that, and Tommy, go away
But it's "the savior of his country" when the band begin to play

That is, when the manager needs someone who can cut code, when the band
begins to play, he doesn't hire a software architect, no matter what
certificates the architect may provide.

> > Sorry you did not get value from the review, but if you do not
share my
> > disquiet about the ways in which some software engineers at one and
the
> > same time use and diss academic computer science, and programming
> > bricolage, then the review wasn't meant for you.
>
> I may indeed share your disquiet; I just have difficulty
understanding what
> you are getting at. Now, maybe that *is* just me.

My disquiet commenced in Silicon Valley in the early 1980s and I
started reading French theory and Frankfurt School critique, along with
technical books, at that time. I was troubled by the promise of
liberation implicit in the early days of the microcomputer and the way
it morphed before my very eyes into real servitude: for example, I went
straight from having to wear as suit and tie to being forbidden to wear
a suit and tie without getting to visit that land where I could dress
as I goddamn well pleased. Foucault speaks directly to the ways in
which power uses apparent pleasure (such as business casual) to attain
ends that may be at variance with human needs.

Ultimately, correct software is a philosophical problem because the
very idea of correctness disappears in virtual reality. Note that in a
computer game, the program does not have to be correct since the world
is the world of the game. Our inability to write correct software may
be due to the fact that increasing computerization and the
virtualization of reality steadily reduces our epistemological
confidence in being able to describe reality, outside of code. By
saying shocking things like "there is nothing but the text", French
theory at least points out the ways in which we're losing our grip.
This is better than happily writing "mindless code" which we never test
against reality, history, common sense, and morality.

Jay

unread,
Nov 30, 2000, 3:00:00 AM11/30/00
to
That review is way to "philosophical" for its own good.

I read the book and its a no brainer that software engineers
need to organize. This is obvious for the following reasons:

(1) Drive up the requirements for software engineers to depress the
number of SEs and increase the status of software engineering,
thus driving up wages, prestige and programmers desirability by hot
chicks.

(2) Drive up the requirements for software engineers so that we don't
have to work with annoying Bozos.

(3) Stop the flooding of the marketplace with cheap labor.

(4) To increase our power over management so that we can create quality
systems, i.e. throw our weight around to stop management Dilbert-like bumbling.

(5) To increase our power over management so that we can jerk their chains
because they are a bunch arrogant assholes.

(6) Increase power over marketing/monopolization forces that make the field
(like M$ tools) so arbitrary and braindead.

etc.

Jay


spino...@my-deja.com wrote:
>
> In article <t2cuv33...@corp.supernews.com>,

Don Chiasson

unread,
Nov 30, 2000, 3:00:00 AM11/30/00
to

spino...@my-deja.com wrote

>............ developers who believe that software
>engineering is Science.

The strength of science lies in the fact that there are
generalizations. Software is engineering in that there
are not generalizations, only improved algorithms
or techniques.


> .......developers


> nonetheless feel at the fact that parts of software
> engineering seem more concerned with dominance
> and control than with Science. I am
> trying to account for the programmers who left
> early structured walkthroughs in tears because their
> world view turned out to be
> inconsistent with the realities of capillary power.
>

The exercise of power in working environment is a reality.
In certain cases, it is a necessity. In far too many others,
it is an ego trip for a manager. It is not unique to
software engineering.

I do not understand the word "capillary." The common
usage is a "minute blood vessel" (Encarta) or "of or like a
hair (of tube, blood vessel, etc.)" (Oxford Dictionary of
Current English).


There is also an equating of truth and power (sorry I
clipped the exact phrase). Life may often exhibit this
characteristic. But, truth can exist independent of power.
It is, unfortunately, also true that power can exist
independent
of truth. (Yes, grammatically I am wrong: I don't like the
way
the word "independently" scans.)

Don


Pete Fenelon

unread,
Nov 30, 2000, 3:00:00 AM11/30/00
to
In alt.folklore.computers Greg Menke <gregm-n...@zxy.mindspring.com> wrote:
> I think he's referring more to the slavish adherence to method over
> substance;

Which reminds me of a CV I reviewed recently for a guy applying
for a software engineering position in the pretty heavily R&D-driven
company I work for... the poor soul actually boasted of his his
ability and willingness to work in an environment completely governed
by inflexible rules. Needless to say, I didn't choose to call him
for interview. I don't think he would've understood me....

pete

spino...@my-deja.com

unread,
Nov 30, 2000, 9:59:00 PM11/30/00
to
In article <3A26C6AB...@jay.jay.org>,

Jay <j...@jay.jay.org> wrote:
> That review is way to "philosophical" for its own good.

Aww, man, I wanted to maintain a high class tone.


>
> I read the book and its a no brainer that software engineers
> need to organize. This is obvious for the following reasons:
>
> (1) Drive up the requirements for software engineers to depress the
> number of SEs and increase the status of software engineering,
> thus driving up wages, prestige and programmers desirability by hot
> chicks.

Yeah, baby!!

But note your low class phraseology is part of the problem set whereas
my high class "philosophical" phraseology is part of the solution set.

First of all, high class phraseology and a philosophical tone has
always been a chick magnet.

Secondly, elites image subordinate classes as motivated by appetite
whereas they, of course, are motivated by pure ideals. This nonsense
was started when Socrates got drunk and started kidding around (cf. The
Republic.) People took his imaginary tale of a disinterested elite, as
contrasted with us bums (motivated as we are by our libido) as the
truth, with the result that George Dubya is a disinterested Guardian of
our interests.

Of course, Woodstock 1999 did show that actually existent slobs are
indeed unqualified to lead themselves, but this may be an artifact of
their subordination to elites, curable after a series of Outward Bound
expeditions. Malcolm X showed us that there is no social change
without personal change. Seattle 1999 showed that people can act right
while diverging from the dominant paradigm. Woodstock 99 was the last
gasp of the silly hippie idea that redemption starts with personal
gratification, and it showed the point at which Foucauldian control
through pleasure fails.

More seriously, consider imagining hot chick scarcity as a social
injustice. That is, software engineers, being for the most part guys,
have guy ways of narrating their lives. Different ways of narrating
our lives may be called for.

If on a Friday night, after a week of 16 hour days essentially fixing
Microsoft's bugs, with the boss blaming us for taking too long and no
time to even ask that hot number out, all we have is The Man Show and
CNN, the fact that we narrate our lives using dominant discourse makes
us feel like losers.

Suppose we started with the demand for emotional justice. Emotional
justice is not a song by the Rolling Stones (that's Emotional Rescue,
see, I'm hip, chukka chukka.) Emotional justice is the unimagined
reverse of the hegemomic situation which we take as a given in the
1990s.

In the hegemonic situation, Americans endure levels of isolation that
shock and disturb visitors from other countries.

Therefore, if we changed the "I'm a loser" narrative to "it is not just
that I do not have a community, in which I might get to talk to people
of the opposite sex without the threat/fear of violence which is used
to separate us" our narrative is less manly but perhaps more useful.
That is, guys narrate themselves as horny when in fact they are lonely.

>
> (2) Drive up the requirements for software engineers so that we don't
> have to work with annoying Bozos.
>

Sounds good.

> (3) Stop the flooding of the marketplace with cheap labor.
>

I support this, except I don't support racist and unworkable labor
protectionism. I support a fair and just free market in capital and
labor worldwide with high levels of unionization.

> (4) To increase our power over management so that we can create
quality
> systems, i.e. throw our weight around to stop management Dilbert-like
bumbling.
>

Yeah baby!!

> (5) To increase our power over management so that we can jerk their
chains
> because they are a bunch arrogant assholes.
>

Sounds great, less filling.

> (6) Increase power over marketing/monopolization forces that make the
field
> (like M$ tools) so arbitrary and braindead.
>

People are preparing for Visual Basic 7 as if it is Godzilla or King
Kong.

> etc.
>
> Jay
>
> spino...@my-deja.com wrote:
> >
> > In article <t2cuv33...@corp.supernews.com>,
>

spino...@my-deja.com

unread,
Nov 30, 2000, 10:25:08 PM11/30/00
to
In article <t2dpg97...@corp.supernews.com>,
"Don Chiasson" <don_ch...@hotmail.com> wrote:
>
> spino...@my-deja.com wrote
>
> >............ developers who believe that software
> >engineering is Science.
>

> The strength of science lies in the fact that there are
> generalizations. Software is engineering in that there
> are not generalizations, only improved algorithms
> or techniques.

I'm not sure this is true. "Go to considered harmful" (letter,
Communications of the ACM, Aug 1968, Edsger Dijkstra) was a
generalization.
>
> > .......developers


> > nonetheless feel at the fact that parts of software
> > engineering seem more concerned with dominance
> > and control than with Science. I am
> > trying to account for the programmers who left
> > early structured walkthroughs in tears because their
> > world view turned out to be
> > inconsistent with the realities of capillary power.
> >
>

> The exercise of power in working environment is a reality.
> In certain cases, it is a necessity. In far too many others,
> it is an ego trip for a manager. It is not unique to
> software engineering.

Absolutely. Software engineering in America shares cultural
understandings with other engineering disciplines.

In American engineering culture in general, the boss has absolute power
over technical decisions when he chooses to exercise that power and
extensive discussion after the decision has been announced is regarded
often as backtalk. As in Leninist "democratic centralism", discussion
is welcomed before the management decision but not after.

It would of course be impossible to run a shop if decisions could be
vetoed in practice for then they would not be decisions. However,
there are successful software departments where people use voting or
the opinions of the team. But because of time pressures and a cultural
understanding (that the 1960s were a mistake, and no more) these shops
are on the wane.

It does appear that in certain cases, foreign software creators are
more successful than Americans owing to different cultural
understanding. Two examples come to mind.

The data base product SAP has been an enormous success because it
essentially seems to have violated the American cultural
commandment "don't reinvent the wheel", for SAP uses a proprietary
interface, essentially a data base, to protect it against changes in
commercial data bases...notably SQL Server. My belief is that SAP,
which was fabricated in Germany, was created this way because "don't
reinvent the wheel" is used in America to discipline ambitious
engineers who have decided that the wheel, like the tires on Ford SUVs,
is broken.

Another example is a clone of Microsoft Office, called Wordstar. When
many programmers learn about Wordstar they feel it is not legal, but as
it happens, it is.

The cultural background for their solicitude for an imagined property
right in the externals of Microsoft Office goes deep. American
engineering culture inherits legal decisions of the 19th century which
made private property NOT ONLY an important right (following Locke) BUT
ALSO the only meaningful right. In the 1850s, the black man was (in
the abominable words of Chief Justice Roger Taney in *Dred Scott*) a
man whose rights no white man need respect. By 1900, this was the man
without property, for in several decisions, the courts found that
private property was the ONLY thing that conferred full humanity.

For example, a manufacturer of flax (a highly inflammable substance)
was allowed in this period to stock it close to a railroad track
despite the fact that excess flax regularly set the wooden steam trains
on fire, a fact which made the railroad men rather sad. It appears
that the Supreme Court of the late 1900s found this a hard case because
no rights (such as the right to be safe from burning flax) could be
based on anything other than ownership.

This, and countless other practices inherited from the 19th century,
influences our thinking: we assume that Microsoft owns the overall
behavior of Office, when in fact Wordstar used its published
documentation to make a somewhat equivalent product.

"Don't reinvent the wheel" is based on the precept of laissez-faire
economics, "the law of comparative advantage." But as a society,
Germany has always been more protective than 20th century America of
its own technology and less willing to use innovations from abroad.
This is because of the greater cultural prestige of German engineers.

A disturbing sidelight is that this German cultural tendency reached
its zenith under Adolf Hitler: in his mad paradise, engineers had a
great deal of power and control, and since the Krauts went to war with
the entire world as soon as possible, they had to reinvent the wheel
along with rubber. I mention this to forestall the usual Internet
tendency to compare views at odds with hegemony to those of Hitler, for
there are modern, non-Fascist societies with greater respect for labor
and engineering.


>
> I do not understand the word "capillary." The common
> usage is a "minute blood vessel" (Encarta) or "of or like a
> hair (of tube, blood vessel, etc.)" (Oxford Dictionary of
> Current English).
>
> There is also an equating of truth and power (sorry I
> clipped the exact phrase). Life may often exhibit this
> characteristic. But, truth can exist independent of power.
> It is, unfortunately, also true that power can exist
> independent
> of truth. (Yes, grammatically I am wrong: I don't like the
> way
> the word "independently" scans.)

My interpretation of Nietzche is that in mediaeval terms he was a
strong nominalist, and believed that truth and power were two names for
the same thing. African philosophy teaches us that many African
peoples were more interested in life-force than in truths that do not
make us whole, and the Buddha lectured his monks on truths that "tend
not to profit."

Perhaps power is what gives us the truth and truth, power. Perhaps
information is less a commodity than a giving up of power, and perhaps
it is being privatized as a way of over-centralizing power.
>
> Don

Jay

unread,
Nov 30, 2000, 10:57:28 PM11/30/00
to
spino...@my-deja.com wrote:

> If on a Friday night, after a week of 16 hour days essentially fixing
> Microsoft's bugs, with the boss blaming us for taking too long and no
> time to even ask that hot number out, all we have is The Man Show and
> CNN, the fact that we narrate our lives using dominant discourse makes
> us feel like losers.

No Way! Bzzzt! Can't happen! With Steve McConnell's vision of our
newly professionalized software engineering field, we will have
software processes and our bosses under control and thus we will
be out by 5PM everyday to which we will hop in our sports
car to go pick the designated hot young babe for that day of the week
(we are talking weekdays here!). Our newly acquired software engineer
desirability would of course requiring special time
scheduling software to keep track of all those dates with the women!

> Therefore, if we changed the "I'm a loser" narrative to "it is not just
> that I do not have a community, in which I might get to talk to people
> of the opposite sex without the threat/fear of violence which is used
> to separate us" our narrative is less manly but perhaps more useful.
> That is, guys narrate themselves as horny when in fact they are lonely.

More seriously. If software was not such a stupid isolating brain dead
rat race, the field would be more desirable and thus attract more women.
A more 50-50 split between women and men in software would of
course benefit the social aspects of the field greatly (and
thus further increase the desirability and prestige of the field)

Jay

Al Dunbar

unread,
Dec 1, 2000, 2:06:27 AM12/1/00
to

<spino...@my-deja.com> wrote in message
news:906d86$lec$1...@nnrp1.deja.com...

> In article <t2cuv33...@corp.supernews.com>,
> "Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
> >
> > <snip - because we have seen it enough times already>

> > I find it odd that you say that it is just me. The initial replies of
> Jason
> > Stokes and Patrick Logan seemed to me to be somewhat in agreement
> with my
> > comments. The fact that the thread has devolved into a discussion,
> however
> > valuable, that nonetheless has no bearing on the book also tends to
> support
> > my view.
> >
> That's great Al. But it's just you, and thousands of other developers
> who share your assumptions and your world-view.

It is ludicrous that you think you have any concept of either my assumptions
or my world-view when my ONLY comment has been that what you labeled as a
review is anything but. Perhaps you spend so much time writing that you have
little time to read the responses, such as the one where I said "I may


indeed share your disquiet; I just have difficulty understanding what you
are getting at."

> > <snip - because we have seen it enough times already>

Al Dunbar

unread,
Dec 1, 2000, 2:18:27 AM12/1/00
to

<spino...@my-deja.com> wrote in message
news:90745i$8vk$1...@nnrp1.deja.com...

> In article <3A26C6AB...@jay.jay.org>,
> Jay <j...@jay.jay.org> wrote:
> > That review is way to "philosophical" for its own good.
>
> Aww, man, I wanted to maintain a high class tone.

Style without substance. I sort of thought that would be something you would
be against, but then, perhaps I still misunderstand you.

> >
> > I read the book and its a no brainer that software engineers
> > need to organize. This is obvious for the following reasons:
> >
> > (1) Drive up the requirements for software engineers to depress the
> > number of SEs and increase the status of software engineering,
> > thus driving up wages, prestige and programmers desirability by hot
> > chicks.
>
> Yeah, baby!!
>
> But note your low class phraseology is part of the problem set whereas
> my high class "philosophical" phraseology is part of the solution set.

Odd, I haven't seen this solution implemented anywhere.

> First of all, high class phraseology and a philosophical tone has
> always been a chick magnet.

OK, OK, I think I finally get what's going on here, people. We are being had
by a Turing experiment gone slightly off its rails. An admirable try on the
output side, but somewhat weak on the input.

<snip - we have already seen enough of this>


Eric Fischer

unread,
Dec 1, 2000, 3:00:00 AM12/1/00
to
<spino...@my-deja.com> wrote:

> Another example is a clone of Microsoft Office, called Wordstar.

WordStar, the classic CP/M word processor of the late 1970s, has
become a clone of Microsoft Office? Is nothing sacred?

(Tangentially related: does anyone know whether the company now
selling CD-ROM drives under the Digital Research name has anything
to do with the Digital Research that was responsible for CP/M?)

eric

Jay Maynard

unread,
Dec 1, 2000, 3:00:00 AM12/1/00
to
On 1 Dec 2000 18:43:04 GMT, Eric Fischer <e...@pobox.com> wrote:

><spino...@my-deja.com> wrote:
>> Another example is a clone of Microsoft Office, called Wordstar.
>WordStar, the classic CP/M word processor of the late 1970s, has
>become a clone of Microsoft Office? Is nothing sacred?

I'd avoided spinoza9999's multi-hundred-line socialist rants after getting
a few lines into the first few and bouncing off the impenetrable rhetoric a
while back...all with a vague feeling that I was mainly bypassing a traincar
load of male bovine exhaust. Thank you for picking out this little gem and
confirming that.

Free clue: WordStar preceded M$ Word by a decade.

Al Dunbar

unread,
Dec 1, 2000, 3:00:00 AM12/1/00
to

"Jay Maynard" <jmay...@thebrain.conmicro.cx> wrote in message
news:ACBDCDA1677757BC.63EFF2E3...@lp.airnews.net...

> On 1 Dec 2000 18:43:04 GMT, Eric Fischer <e...@pobox.com> wrote:
> ><spino...@my-deja.com> wrote:
> >> Another example is a clone of Microsoft Office, called Wordstar.
> >WordStar, the classic CP/M word processor of the late 1970s, has
> >become a clone of Microsoft Office? Is nothing sacred?
>
> I'd avoided spinoza9999's multi-hundred-line socialist rants after getting
> a few lines into the first few and bouncing off the impenetrable rhetoric
a
> while back...all with a vague feeling that I was mainly bypassing a
traincar
> load of male bovine exhaust. Thank you for picking out this little gem and
> confirming that.

So, perhaps it's NOT just me! :-)

/Al


Eric Smith

unread,
Dec 1, 2000, 3:00:00 AM12/1/00
to
Giles Todd <g...@at-dot.org> writes:
> My point was that there must come a stage where discussion stops and
> focussed activity starts.

Amen, brother! Let's form a planning committee to develop a list of
action items.

spino...@my-deja.com

unread,
Dec 1, 2000, 8:49:49 PM12/1/00
to
In article
<ACBDCDA1677757BC.63EFF2E3...@lp.airnews.net>,

jmay...@conmicro.cx wrote:
> On 1 Dec 2000 18:43:04 GMT, Eric Fischer <e...@pobox.com> wrote:
> ><spino...@my-deja.com> wrote:
> >> Another example is a clone of Microsoft Office, called Wordstar.
> >WordStar, the classic CP/M word processor of the late 1970s, has
> >become a clone of Microsoft Office? Is nothing sacred?
>
> I'd avoided spinoza9999's multi-hundred-line socialist rants after
getting
> a few lines into the first few and bouncing off the impenetrable
rhetoric a
> while back...all with a vague feeling that I was mainly bypassing a
traincar
> load of male bovine exhaust. Thank you for picking out this little
gem and
> confirming that.

Sorry for the typo. The product name is StarOffice. It's likely you
are ignorant of the product.

Furthermore: if the style of the original post was offputting it is
then not intended for you. As I have indicated, hatred of what is
misnamed wordiness can be hatred of language itself, and the desire of
some software engineers to free themselves of the tests of history,
language, morality and common sense.

spino...@my-deja.com

unread,
Dec 1, 2000, 9:34:18 PM12/1/00
to
In article <3A272219...@jay.jay.org>,

Jay <j...@jay.jay.org> wrote:>
> More seriously. If software was not such a stupid isolating brain dead
> rat race, the field would be more desirable and thus attract more
women.
> A more 50-50 split between women and men in software would of
> course benefit the social aspects of the field greatly (and
> thus further increase the desirability and prestige of the field)
>
> Jay

In many ways, the presence of women professionals in the field raises
the tone. Steve book has an example: the NASA group he describes is
more equitable than the normal group.

This group uses modern software engineering practises and people
typically leave work at a reasonable hour (Steve makes what I think is
a major error here: he ascribes the reasonableness of the hour to the
practices: it's probably the fact that these are government employees
not as subject to death-march schedules, and NASA, post-Challenger, is
wary of death-march schedules.)

Women tend not to want to work the animalistic work hours that male
software engineers work, and this is a virtue.

However, they introduce strains of their own. Deborah Tannen is a
researcher on gender-differentiated styles of computer use, and she's
shown that the virtue and vice of male technicians is their willingness
to push the envelope and take risk, whereas on the whole the virtue and
vice of women engineers is their willingness to slow down and go by the
book. Women are sometimes just afraid of programmers actually
programming, and in my view they are a major force in downsizing and
deskilling as they discourage their programmers from programming.

Women also remind us of the fact that when the modern fully respected
professions of medicine and law were formed in the USA, the formation
was an occasion of extreme sex discrimination. Part of the reason
doctors organized into the modern medical profession was quite
consciously to eliminate the profession of midwife and the women who
assisted in abortions. Even in the early 1960s, women were rare in law
schools, and had to put up with a great deal of hijinx when they did
attend.

This sort of sex discrimination could be institutionalized if
programming became a profession on Steve's model.

Already, Microsoft testing is primarily informed by adolescent male
competitive values for it's whole theme is "you think you so smart."
Many of its questions constitute what I regard (as an adjunct faculty
member) as educational malpractice. I was saddened and astonished,
even though I'm Microsoft certified, to see a woman coworker fail a
Microsoft test repeatedly although she had an advanced degree from a
European university.

Tests in general are biased towards students of higher social class,
and Microsoft tests are biased towards the sort of guy who likes
solving puzzles rather than real problems. They also overemphasize
using Microsoft solutions that at times are inferior to third-party
solutions and so-called "reinventing the wheel."

The extraordinarily poor design of Microsoft tests led, a few years
ago, to cynical gamesmanship in which "boot camps" (another male
metaphor) taught completely unqualified people the answers by rote, and
there has been considerable dishonesty within corporations that require
Microsoft test-takers to "teach" others...by giving them the questions
and the correct answers.

Steve's book is simply uninformed of the cultural and historical matrix
in which the modern full professions of law, medicine and traditional
engineering took place. Although they were formed in the sexism and
racism of the late 19th century, they matured during a liberal phase of
American history which actually encouraged people to better themselves
by becoming professionals, and which reluctantly but steadily welcomed
women and nonwhites into the ranks of professionals.

Our time is considerably different. To be gracious about entry into an
upper middle class profession, whether one's own entry or another's, is
taken as a sign of weakness, for due to the very collapse of tradition,
we're all fighting for the same diminishing pie.

The very opening of the legal profession, while necessary and just, led
in our society to unprecedented levels of despair among actual lawyers
as they no longer were made to feel as if they were "special". They
instead discovered that becoming an associate in a law firm involved
just another paper chase to make partner (as adjunct faculty yearn for
tenure) and they discovered that their work, similar to much work in
data processing, was so much under the control of mega firms and their
mega mega clients that it had no meaning.

The result is that when people talk about professional issues in many
fields including computing, their talk is less about ideals and more
about who gets what. "I'm a doctor and you're not", "I'm a lawyer and
you're not", and "I'm a software engineer and you're not" are slogans,
the form of which appeared in the 1970s as people realized that
traditional forms of distinction were on the wane, but was not (thanks
to the economy) about to replaced by a paradise of equality.

In Minnesota poet Robert Bly's vision of the "sibling society",
the "grownups", those who are professionals or who seek to
professionalize, unconsciously become children chanting "I'm a software
engineer and you're not", or "ha ha ha, you flunked your Microsoft
exam." In Bly's view they do so precisely because their elder siblings
have abandoned history and culture (as Steve unconsciously does, by
reducing software engineering to technology) and placed themselves, and
everybody else, into an insane struggle for place and position.

This nasty brew is not a good place to start testing programmers for
legal certification. A better solution would be to let the free market
decide who's a software engineer, and for the software engineers to
organize, not professional societies, but trade unions. Instead of
reducing programmers to tears with poorly designed examinations or
structured walkovers, the union hall would teach and mentor
programmers, and help them find jobs. Through solidarity, it would be
a place of healing, as well as a great place to meet hot chicks :-).

spino...@my-deja.com

unread,
Dec 1, 2000, 9:59:06 PM12/1/00
to
In article <t2ek63e...@corp.supernews.com>,

"Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
>
> <spino...@my-deja.com> wrote in message
> news:90745i$8vk$1...@nnrp1.deja.com...
> > In article <3A26C6AB...@jay.jay.org>,
> > Jay <j...@jay.jay.org> wrote:
> > > That review is way to "philosophical" for its own good.
> >
> > Aww, man, I wanted to maintain a high class tone.
>
> Style without substance. I sort of thought that would be something
you would
> be against, but then, perhaps I still misunderstand you.
>
> > >
> > > I read the book and its a no brainer that software engineers
> > > need to organize. This is obvious for the following reasons:
> > >
> > > (1) Drive up the requirements for software engineers to depress
the
> > > number of SEs and increase the status of software engineering,
> > > thus driving up wages, prestige and programmers desirability by
hot
> > > chicks.
> >
> > Yeah, baby!!
> >
> > But note your low class phraseology is part of the problem set
whereas
> > my high class "philosophical" phraseology is part of the solution
set.
>
> Odd, I haven't seen this solution implemented anywhere.

Norwegian computer consultant Tom Gilb authored some excellent books on
software engineering and humanized input in the 1970s. He's also
written about what he calls the "Scandinavian critical model" of
computer science, which gives a greater level of respect and visibility
to data processing labor.

Gilb's theories about "humanized input" became the ergonomics of the
1990s and indirectly influenced the design of the Macintosh. They seem
to derive from the culture of Scandinavian societies, in which the
keypunch operator of the 1970s was not invisible or a form of lowlife
but a person, a citizen, demanding recognition and respect ON THE
JOB...in the form of data processing systems that (instead of
monitoring her for "productivity") used the computer to supply
reasonable and labor saving defaults, and to error check in a labor
saving rather than hostile way.

Here in the States, even today, many companies use keystrokes per
minute as a measure of "productivity": this measure takes as a given
that the keystrokes are the mininum necessary, and, in the States, this
is considered to be a closed question, answered by management once and
for all.

Gilb's work also made visible (as did the contemporary structured
programming revolution) the need of the programmer for some sense of
comprehension and mastery. When structured programming began it was
invented by programmers to save themselves time and to attain some
needed control over their work lives: but because in our culture the
worker is supposed (when push comes to shove) to abandon this in favor
of income, structured programming was gradually taken over by
management.

But Gilb, in his more modern work, has preserved a moderately pro-
labor, critical stance. In a recent article, he has clearly enough
stated that computing snafus are almost never the fault of incompetent
and/or lazy programmers, but of poor management decisions.

"Critical data processing" has been all over the world a source of
quiet success stories. Now, it is true that the people who take a
humanistic, compassionate, and moderately pro-labor stance in their
work don't read Foucault, and lack my taste for going on and on like I
do. The problem is that they cannot form a coherent intellectual
defense, even in their internal monologues, when their successful,
compassionate work-group is taken over by Sharks Is Us, Inc. They are
thus voiceless (even in their internal monologue) when dragooned into
such marvelous Bad Ideas such as Rigid Limits on Software Design (a
real methodology which admits of NO changes to deadlines) or Peoplesoft.

I am somewhat arrogantly trying to give a name and form to what I have
seen as success in software development and universally it seems to me
that software is most successful when it is critical, human, pro-labor,
compassionate. Of course, I do not mean financial success,
necessarily. I mean instead a holistic success in which NO
stakeholder, including the programmers, pay for the success with
exhaustion, broken marriages, and other tragedies.


>
> > First of all, high class phraseology and a philosophical tone has
> > always been a chick magnet.
>
> OK, OK, I think I finally get what's going on here, people. We are
being had
> by a Turing experiment gone slightly off its rails. An admirable try
on the
> output side, but somewhat weak on the input.
>

Sorry you feel that way. I am not a Turing experiment although I am
almost as weird as Turing was.


> <snip - we have already seen enough of this>
>
>

Jay Maynard

unread,
Dec 1, 2000, 10:38:59 PM12/1/00
to
On Sat, 02 Dec 2000 01:49:49 GMT, spino...@my-deja.com
<spino...@my-deja.com> wrote:
>Sorry for the typo. The product name is StarOffice. It's likely you
>are ignorant of the product.

Not bloody likely, considering it's one that I use semi-regularly, mostly in
the hope that it'll deal with the garbage that the latest incarnation of the
M$ atrocities put out.

>Furthermore: if the style of the original post was offputting it is
>then not intended for you. As I have indicated, hatred of what is
>misnamed wordiness can be hatred of language itself, and the desire of
>some software engineers to free themselves of the tests of history,
>language, morality and common sense.

I do not dislike wordiness, and I believe that language, properly used, is a
tool of great power and elegance. Your great mistake when writing is in
believing that verbosity can make up for utter lack of content or critical
thinking.

Have a nice life.

*plonk*

Andy Rabagliati

unread,
Dec 1, 2000, 6:09:37 PM12/1/00
to
According to Eric Fischer <e...@pobox.com>:

> <spino...@my-deja.com> wrote:
>
> > Another example is a clone of Microsoft Office, called Wordstar.
>
> WordStar, the classic CP/M word processor of the late 1970s, has
> become a clone of Microsoft Office? Is nothing sacred?

Who launched WordStar2000, with different keybindings, and
wrote their own death warrant ?

Cheers, Andy! http://www.wizzy.com/andyr/Mel.html

Andy Dingley

unread,
Dec 2, 2000, 3:00:00 AM12/2/00
to
spino...@my-deja.com a écrit :

>It's just you, Al. The review is not meant to be a "consumer guide",
>or ersatz for reading the book.

So why not post it to alt.black-turtle-neck or
alt.sex.masturbation.literary instead ?

>The review is instead critique that airs views about "software
>engineering" that seldom see print.

So why title it as a review ?

If you _want_ to ponce about with lit-crit theory, then don't do it in
here. We've got better things to do.

--
Smert' Spamionam

spino...@my-deja.com

unread,
Dec 3, 2000, 12:06:43 AM12/3/00
to
In article
<02751A529940BEF6.233D7DE0...@lp.airnews.net>,

I have found that people who are quick with the charge of prolixity use
it as a timesaver when they simply do not care, for a good reason, a
bad reason, or no reason at all, to address the issues that were
raised. You haven't explained the lack of content, and as for critical
thinking, your comment here seems to indicate you did not even read the
post: for I've pointed out the ways in which software engineering is
presented in an anti-critical context, and in which programmers who
object to its deskilling implications are categorised, without
reflection, and Luddites.

For a good example of this, please see the editorial comments on the
Amazon web site concerning Steve's book. In their interest in brevity
(which here, as elsewhere, is not really an aesthetic interest at all,
but instead imposed by external economic pressures) the unnamed writers
of the comment cut to the chase: for they immediately characterize
software engineering, not as a positive scientific advance or
engineering innovation, but as a disciplinary measure, sure to put the
Luddites to flight.

In fine, I am extremely offended by your comment concerning my putative
lack of critical thinking. The charge of verbosity may be thought
justly by some to have merit (note that a committment to truth compels
me to phrase this very thought with prolixity, since I wanted at one
and the same time to be charitable and hold fast to my own conviction
that there are precisely enough words, no more and no less.)

But as I have indicated, I began reflecting on these issues in 1981 and
did not express them because I perceived that "software engineering"
was really a disciplinary measure, and I perceived the hazard of the
thought to my career and the futures of my children, at that date quite
young. I perceive myself as being quite the critical thinker because
I've given voice to such an antinominian view, and therefore I am
offended by what you've said.

What you've said illustrates my point that Foucault's theory of
capillary power is relevant to software engineering, for the charge of
verbosity is in my observation used by subordinate intellectuals to
discipline threats from source even more subordinate. Strikingly, what
attracts it is not only word count and the use of subordinate phrases
but also grammatical accuracy and lack of spelling errors.

We're all in Pharaoh's army, as Steve McConnell unconsciously knows,
overseen not by Egyptians, but by fellow Israelites whose fear of
Pharaoh wields the whip.

spino...@my-deja.com

unread,
Dec 3, 2000, 12:11:00 AM12/3/00
to
In article <t2gkmh...@corp.supernews.com>,

"Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
>
> "Jay Maynard" <jmay...@thebrain.conmicro.cx> wrote in message
>
news:ACBDCDA1677757BC.63EFF2E3...@lp.airnews.net..
.
> > On 1 Dec 2000 18:43:04 GMT, Eric Fischer <e...@pobox.com> wrote:
> > ><spino...@my-deja.com> wrote:
> > >> Another example is a clone of Microsoft Office, called Wordstar.
> > >WordStar, the classic CP/M word processor of the late 1970s, has
> > >become a clone of Microsoft Office? Is nothing sacred?
> >
> > I'd avoided spinoza9999's multi-hundred-line socialist rants after
getting
> > a few lines into the first few and bouncing off the impenetrable
rhetoric
> a
> > while back...all with a vague feeling that I was mainly bypassing a
> traincar
> > load of male bovine exhaust. Thank you for picking out this little
gem and
> > confirming that.
>
> So, perhaps it's NOT just me! :-)

Note the epistemological crisis Al has undergone, for he confessed to a
vague disquiet. But the crisis is resolved by marginalizing the
messenger and thus old Al is all relieved, for it's basically harder to
question institutional power than to marginalize an individual.

Yes, Al, you can return to the Dilbertized herds who at one and the
same time resent and replicate illegitimate authority.

>
> /Al

spino...@my-deja.com

unread,
Dec 3, 2000, 12:19:25 AM12/3/00
to
In article <saig2tk6cam7csab2...@4ax.com>,

Andy Dingley <din...@codesmiths.com> wrote:
> spino...@my-deja.com a écrit :
>
> >It's just you, Al. The review is not meant to be a "consumer guide",
> >or ersatz for reading the book.
>
> So why not post it to alt.black-turtle-neck or
> alt.sex.masturbation.literary instead ?

Because it happens to be a serious professional concern.

The State of Virginia bought into the rhetoric about software
engineering, especially its brutal implementation of the law of
comparative advantage, and for this reason contracted with Peoplesoft
to implement a human resources system. Peoplesoft's approach was based
on the unproven idea that software written for private business would
work for a unionized public agency, but this was accepted because it
was felt that an in-house system would be "reinventing the wheel."

This neglected the fact that the structure of the system's stakeholders
was completely different from the customers and the employees of a
private business, and the result was that Peoplesoft consultants
(charging almost 200.00 per hour) and in house programmers wasted FIVE
YEARS and got nowhere.

The critical and most needed parts of the system were then rewritten,
in house, by a new team using the Web.

The only sensible explanation of this mess lies in literary critical
theories of reification...in which we make a thing of a word. Computer
programs are not things, therefore it was folly of the State of
Virginia to think that an off the shelf system would work.


>
> >The review is instead critique that airs views about "software
> >engineering" that seldom see print.
>
> So why title it as a review ?
>
> If you _want_ to ponce about with lit-crit theory, then don't do it in
> here. We've got better things to do.
>

Gee, that sounds like good old fashioned censorship to me.
> --
> Smert' Spamionam

naisbodo

unread,
Dec 3, 2000, 1:28:46 AM12/3/00
to
In comp.programming spino...@my-deja.com wrote:

> Yes, Al, you can return to the Dilbertized herds who at one and the
> same time resent and replicate illegitimate authority.

You're obviously heavily into discursive study. There's a lot of work
done with respect to discursive ideals and philosophy which is heavily
jargon-laden, because that jargon is the best way to communicate those
ideas being discussed within that field.

However, when you venture outside of that largely academic field into
the real world, so to speak, you have to be prepared to deal with people
on *their* level. That is, you have to translate your jargon into lay
terms. If you fail to do so, it's entirely your own fault when you
receive negative responses, if only because it's an eminently possible
and reasonable requirement.

> Note the epistemological crisis Al has undergone, for he confessed to a
> vague disquiet. But the crisis is resolved by marginalizing the
> messenger and thus old Al is all relieved, for it's basically harder to
> question institutional power than to marginalize an individual.

This is of course an egregious aggrandizement bolstered by relentless
grandiloquence with little substantive justification, and one easily
applied back to its framer. Your indictment of his marginalization
performatively contradicts itself through self-description; perhaps
if your final clause, ostensibly justifying your ad hominem, were less
nonsequitous it would not so obviously betray its rhetorical nature.

If you are not a troll, you will quickly realize the effect of overly
formal diction in an informal context. Please, desist in your abuse
of formality, and adapt to the groups within which you post. Failure
to do so is simply rude.

--
nais...@enteract.com
http://www.naisbodo.com/

Greg Menke

unread,
Dec 3, 2000, 3:00:00 AM12/3/00
to
>
> Because it happens to be a serious professional concern.
>
> The State of Virginia bought into the rhetoric about software
> engineering, especially its brutal implementation of the law of
> comparative advantage, and for this reason contracted with Peoplesoft
> to implement a human resources system. Peoplesoft's approach was based
> on the unproven idea that software written for private business would
> work for a unionized public agency, but this was accepted because it
> was felt that an in-house system would be "reinventing the wheel."
>
> This neglected the fact that the structure of the system's stakeholders
> was completely different from the customers and the employees of a
> private business, and the result was that Peoplesoft consultants
> (charging almost 200.00 per hour) and in house programmers wasted FIVE
> YEARS and got nowhere.
>
> The critical and most needed parts of the system were then rewritten,
> in house, by a new team using the Web.
>
> The only sensible explanation of this mess lies in literary critical
> theories of reification...in which we make a thing of a word. Computer
> programs are not things, therefore it was folly of the State of
> Virginia to think that an off the shelf system would work.
> >

The Dept. of Energy has had a similar experience with PeopleSoft. "6
months" was the first quote- at the end of which, the system couldn't
generate the first of the important reports. Its been about 3 years
now, so I imagine its probably gotten somewhat better, but I'd be very
surprised indeed if the new system is actually operating. So thats 3
years of paying a bunch of $200/hr people to learn requirements and
implement them- and thats before you add the incidental support costs
of trying to get Windows to work reliably. "COTS" indeed.

A complete rewrite of the system by the mainframe systems people who
had been maintaining it would almost certainly be substantially
cheaper, not to mention easier.

Gregm

donald tees

unread,
Dec 3, 2000, 3:00:00 AM12/3/00
to
spino...@my-deja.com wrote in message <90ckd1$c49$1...@nnrp1.deja.com>...
>In article

>
>What you've said illustrates my point that Foucault's theory of
>capillary power is relevant to software engineering, for the charge of
>verbosity is in my observation used by subordinate intellectuals to
>discipline threats from source even more subordinate. Strikingly, what
>attracts it is not only word count and the use of subordinate phrases
>but also grammatical accuracy and lack of spelling errors.
>
>We're all in Pharaoh's army, as Steve McConnell unconsciously knows,
>overseen not by Egyptians, but by fellow Israelites whose fear of
>Pharaoh wields the whip.

I was amused by these paragraphs. The writing is so verbose, it is
difficult to tell if it is really a post against pomposity, sarcasm, or just
amusing.

I've written software for thirty years now. I've read a book a day, on
the average, since I was about ten. That was in 1956. I think that when
I have to make notes about a 500 word post, then sit down and analyse
it for ten minutes before I can figure out what the poster means,
that there is something wrong with the writing.

Strangely enough, I think I agree, slightly, with what you are trying
to say. I think that perhaps, over five or six arguments, I have come
to a slight understanding as to what you are attempting to express.

However, esoterical expression does not make a theory correct. It is
merely an academic device to boost ego. A good programmer can
express it so even a computer (and maybe a few dumb programmers)
can understand it. That takes a certain skill.

As to the amusement. I think "software engineering" an academic
pomposity foisted upon us in direct response to the pomposity evident
in articles such as yours. They are one and the same thing, just aimed
in the opposite direction.


Al Dunbar

unread,
Dec 3, 2000, 3:00:00 AM12/3/00
to

<spino...@my-deja.com> wrote in message
news:90ckl2$cdv$1...@nnrp1.deja.com...

> In article <t2gkmh...@corp.supernews.com>,
> "Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
> >
> > "Jay Maynard" <jmay...@thebrain.conmicro.cx> wrote in message
> >
> news:ACBDCDA1677757BC.63EFF2E3...@lp.airnews.net..
> .
> > > On 1 Dec 2000 18:43:04 GMT, Eric Fischer <e...@pobox.com> wrote:
> > > ><spino...@my-deja.com> wrote:

<<snip>>

> > > I'd avoided spinoza9999's multi-hundred-line socialist rants after
> getting
> > > a few lines into the first few and bouncing off the impenetrable
> rhetoric
> > a
> > > while back...all with a vague feeling that I was mainly bypassing a
> > traincar
> > > load of male bovine exhaust. Thank you for picking out this little
> gem and
> > > confirming that.
> >
> > So, perhaps it's NOT just me! :-)
>
> Note the epistemological crisis Al has undergone, for he confessed to a
> vague disquiet. But the crisis is resolved by marginalizing the
> messenger and thus old Al is all relieved, for it's basically harder to
> question institutional power than to marginalize an individual.

My reference to a vague disquiet was no more a "confession" than was yours.
In actual fact, it was an attempt to extend a symbolic hand of
non-disagreement with you on certain points. The fact that these points of
possible agreement have very little to do with the subject line (book
review), has already been discussed in this thread.

> Yes, Al, you can return to the Dilbertized herds who at one and the
> same time resent and replicate illegitimate authority.

First, I think that the majority of other posts have generally confirmed
that it is not just me.

Second, for all of your attempts to sound more philosophical than the rest
of us, your excess verbiage tends to hide the fallacy of your own
conclusions. One of these being that those who disagree with your viewpoints
must all belong to the moral low-road simply because yours is the high road,
or at least you imply that it is.

Another is the fallacy that "if you disagree with me on this one point, then
it must be that you disagree with me on all points".

Another is your contention that my apparent decision to "marginalize" you is
my way of resolving my apparent "epistemological crisis" by taking the easy
way out because it is easier to do so than to question institutional power.
An alternate view, that would be much easier for you to consider were you
the sort of person who could at least theorize the possibility that you are
not always right on all points, could be that my expressed views happen to
represent what I think. The easy way is not always wrong, and the hard way
is not always correct. If they were, then, by definition, it would always be
easy to determine what is correct -- you would just always take the
difficult choice.

Another is that you, more than me, are the one using marginalization
techniques in order to avoid having to consider and address the arguments of
the other side.

/Al

Al Dunbar

unread,
Dec 3, 2000, 3:00:00 AM12/3/00
to

<spino...@my-deja.com> wrote in message
news:909ohp$coc$1...@nnrp1.deja.com...

> In article <t2ek63e...@corp.supernews.com>,
> "Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
> >
> > <spino...@my-deja.com> wrote in message
> > news:90745i$8vk$1...@nnrp1.deja.com...
> > > In article <3A26C6AB...@jay.jay.org>,
> > > Jay <j...@jay.jay.org> wrote:

<<<snip>>>

> > > But note your low class phraseology is part of the problem set
> whereas
> > > my high class "philosophical" phraseology is part of the solution
> set.
> >
> > Odd, I haven't seen this solution implemented anywhere.
>
> Norwegian computer consultant Tom Gilb authored some excellent books on
> software engineering and humanized input in the 1970s. He's also
> written about what he calls the "Scandinavian critical model" of
> computer science, which gives a greater level of respect and visibility
> to data processing labor.

In deference to Mr. Gilb, whose works I have not read, I would assume that
his "high class phraseology" was combined with actual content, rather than
simply being there for its own sake.

<<snip - not because I disagree, just because there is too much text here>>

> I am somewhat arrogantly trying to give a name and form to what I have

"somewhat"? :-)

> seen as success in software development and universally it seems to me
> that software is most successful when it is critical, human, pro-labor,
> compassionate. Of course, I do not mean financial success,
> necessarily. I mean instead a holistic success in which NO
> stakeholder, including the programmers, pay for the success with
> exhaustion, broken marriages, and other tragedies.

Sorry, but, on this point at least, I will have to AGREE with you. I would
bet, however, that many of those people whose lives you want to protect from
abuse perpetrated on them by the establishment would get not much more than
a good laugh out of your verbose rants on their behalf. You would likely say
that that is because they are not your philosophical equal. To that I say I
am glad.

> >
> > > First of all, high class phraseology and a philosophical tone has
> > > always been a chick magnet.
> >
> > OK, OK, I think I finally get what's going on here, people. We are
> being had
> > by a Turing experiment gone slightly off its rails. An admirable try
> on the
> > output side, but somewhat weak on the input.
> >
> Sorry you feel that way.

Actually, I do not feel that way. I have often suspected your inability to
understand what others say; it appears that sarcasm is just one more thing
you have difficulty discerning. :-)

> I am not a Turing experiment although I am
> almost as weird as Turing was.

This fact has been made abundantly clear.

/Al

spino...@my-deja.com

unread,
Dec 3, 2000, 3:00:00 AM12/3/00
to
In article <90dl73$pc0$1...@news.igs.net>,
"donald tees" <don...@willmack.com> wrote:
> spino...@my-deja.com wrote in message <90ckd1$c49
$1...@nnrp1.deja.com>...
> >In article

>
> >
> >What you've said illustrates my point that Foucault's theory of
> >capillary power is relevant to software engineering, for the charge
of
> >verbosity is in my observation used by subordinate intellectuals to
> >discipline threats from source even more subordinate. Strikingly,
what
> >attracts it is not only word count and the use of subordinate phrases
> >but also grammatical accuracy and lack of spelling errors.
> >
> >We're all in Pharaoh's army, as Steve McConnell unconsciously knows,
> >overseen not by Egyptians, but by fellow Israelites whose fear of
> >Pharaoh wields the whip.
>
> I was amused by these paragraphs. The writing is so verbose, it is
> difficult to tell if it is really a post against pomposity, sarcasm,
or just
> amusing.

I should mention at this point that I am a published author, have been
for about twenty years, and finally that I am under contract to write a
book on software.

Now, this in itself does not indicate that I am not verbose. The only
accurate definition of verbosity lies not in raw word count but in the
RATIO of words to needed and/or original ideas.

The problem is that this ratio is not surd, for there is no such thing
as counting when it comes to ideas. What we count is always the token:
the expression in words of the idea. This is illustrated by the fact
that we find that ideas are sometimes equivalent.

The charge of prolixity is all too often technically Fascist since it
purposely mistakes, for verbosity, a density of new, surprising, anti-
nominian and otherwise disquieting ideas.

There are overly verbose writers. I used to work for an ex-IBMer who
wrote a series of books on the IBM System/3, a forerunner of the
AS/400, Jerome Murray. I found his books absurdly pompous and verbose,
and initially I found Jerry pompous and verbose in person.

However, he was the first adult male to notice that I knew how to
program in assembly language and he encouraged me to pursue a
programming career. I happen to value the ornate and verbose way in
which he expressed these thoughts as opposed to the deafening and cruel
silence with which most adult males in business treat kids.

Also, years later I found that he had joined a conservative Catholic
organization (Opus Dei.) While Opus Dei is on the opposite end of the
political spectrum from yours truly, this made it clear to me that part
of the reason for Jerry's verbosity was identical to part of the reason
for my own verbosity.

It was cultural. Both Jerry and I had been educated by Catholic
priests who gave higher grades to longer papers IF there were no errors
in grammar and spelling. Educated Roman Catholics share with educated
Arabs, and other cultures supposed more primitive than American free-
market Protestantism, a love of language whereas in the dominant
culture time and language are forms of money...with which one is
supposed to be somewhat anal-compulsive.

I thus have an identity politics claim that I am being discriminated
against because of cultural prejudice, but I'd prefer to get beyond
this wearisome discussion of verbosity. I feel that many posters in
this thread are using the charge because they do indeed share my
disquiet at the brutalization and reification of software developers,
but are afraid for their own position in society.


>
> I've written software for thirty years now. I've read a book a day,
on
> the average, since I was about ten. That was in 1956. I think that
when
> I have to make notes about a 500 word post, then sit down and analyse
> it for ten minutes before I can figure out what the poster means,
> that there is something wrong with the writing.

That may well be, for all have sinned.

>
> Strangely enough, I think I agree, slightly, with what you are trying
> to say. I think that perhaps, over five or six arguments, I have come
> to a slight understanding as to what you are attempting to express.

Cool.


>
> However, esoterical expression does not make a theory correct. It is

No. But there must be an explanation of Gresham's law ("99 percent of
everything is crap.") Perhaps thought of truly high quality is like
Olympic sport with its own severe demands. When I ran the London
Marathon, I had to live, sleep and breathe the London Marathon, and I
had to become an esoteric adept at marathon running. Why should
software be any different?

> merely an academic device to boost ego. A good programmer can
> express it so even a computer (and maybe a few dumb programmers)
> can understand it. That takes a certain skill.
>
> As to the amusement. I think "software engineering" an academic
> pomposity foisted upon us in direct response to the pomposity evident
> in articles such as yours. They are one and the same thing, just
aimed
> in the opposite direction.

You don't recall the attacks made on academic computer science by Steve
McConnell.

There is a sharp distinction between the sort of academic careerism and
pomposity found in traditional humanities departments, and the parallel
phenomenon found in business schools.

In both venues, the faculty enjoy protection from the marketplace. In
public and first-tier private schools, the protection for English and
computer science faculty is provided by the taxpayers or the endowment.

The business school professors like to think of themselves as more
attached to the free market but they, too, are isolated from the REAL
free market by a combination of public respect for education (any
education) and a vast and growing network of pro-business funds and
think-tanks, as well as the unquestioned (and nearly criminal)
diversion of public funds into support for "free" market ventures.

McConnell's "software engineering" is more a business school
phenomenon. Now apart from the technicalities of public accounting,
business schools add or transmit precious little to or from the stock
of human knowledge. Their main function is to manufacture consent to
the proposition that the business of America is business, which
involves, in software engineering, avoiding "disruption" as we build
the modern Pyramids.

You are perfectly correct in saying that parts of software engineering
are academic pomposities, and in believing that many English lit-crit
types are frauds. However, they are pompous frauds in their own way,
and probably because of Gresham's law.

But just as we find the occasional gem (such as the work of Richard
Rorty or Martha Nussbaum) in the general muck of humanities culture, we
ALSO find good ideas in B school work. If few add to or transmit from
human knowledge *per se*, their value nonetheless resides in the way
they enhance people's lives, by, for example, showing them how to
program in Visual Basic, and thereby earn a living without selling
drugs. Some of the work done at the private, for-profit University of
Phoenix is first rate, for example. If the B schools got back to their
original idea, which was preparing working slobs for a better life, and
out of neoconservative horseshit, they'd find their soul.

spino...@my-deja.com

unread,
Dec 3, 2000, 3:00:00 AM12/3/00
to
In article <90cp6u$p5v$1...@bob.news.rcn.net>,

naisbodo <nais...@enteract.com> wrote:
> In comp.programming spino...@my-deja.com wrote:
>
> > Yes, Al, you can return to the Dilbertized herds who at one and the
> > same time resent and replicate illegitimate authority.
>
> You're obviously heavily into discursive study. There's a lot of work
> done with respect to discursive ideals and philosophy which is heavily
> jargon-laden, because that jargon is the best way to communicate those
> ideas being discussed within that field.
>
> However, when you venture outside of that largely academic field into
> the real world, so to speak, you have to be prepared to deal with
people
> on *their* level. That is, you have to translate your jargon into lay
> terms. If you fail to do so, it's entirely your own fault when you
> receive negative responses, if only because it's an eminently possible
> and reasonable requirement.

Thanks for this thoughtful comment.

Last year I gave a rather verbose talk "Was Theodore Adorno a Schnook
or a Good Guy?" at Chicago's famous "hobo college", The College of
Complexes.

A left-wing high school teacher took me to task in your thoughtful way.

However, the demand, thought to be egalitarian, reasonable and fair,
that one speak the speech of Da People as a prior requirement that gets
to "trump" or supersede the nondistortion of the message, is part of
the overall culture of dominance. Read Adorno himself for the
(ultimately) common-sense observation that oppression squeezes the
ability to think complex thoughts out of the victim class.

Besides, George Dubya should make it clear that their is nothing
egalitarian about oversimplified speech. He and his goddamn father
both used oversimplified biz-speech in order to cover up their
monkeyshines, and his goddamn father learned this skill in the Central
Intelligence Agency. Just as we funded military dictators in the 1970s
who spoke simply and brutally to their people "get to work and shut the
fuck up", this particular chicken is coming home to roost.

>
> > Note the epistemological crisis Al has undergone, for he confessed
to a
> > vague disquiet. But the crisis is resolved by marginalizing the
> > messenger and thus old Al is all relieved, for it's basically
harder to
> > question institutional power than to marginalize an individual.
>
> This is of course an egregious aggrandizement bolstered by relentless
> grandiloquence with little substantive justification, and one easily
> applied back to its framer. Your indictment of his marginalization
> performatively contradicts itself through self-description; perhaps
> if your final clause, ostensibly justifying your ad hominem, were
less
> nonsequitous it would not so obviously betray its rhetorical nature.
>

The difference between you obvious satire is that I have a real social
and political goal, and where my syntax is complex it is actually
trying to be fair. Your nasty purpose is the opposite, and it is to
make fun of me. I have no personal problem with this for believe it or
not I do not take myself all that seriously. My concern is that this
pre-emptive debate about prolixity forestalls any real discussion of
the ways in which software developers are being materially screwed.

> If you are not a troll, you will quickly realize the effect of overly
> formal diction in an informal context. Please, desist in your abuse
> of formality, and adapt to the groups within which you post. Failure
> to do so is simply rude.
>

No, I will NOT adapt to the group in which I post. That is because the
Internet statistically over-represents the worst elements in our
society, weighted as it is towards physical cowards, truly pompous neo-
conservatives, Ku Kluxers, and people like Scientologists and Holocaust
deniers who use the lack of friction implicit in electronic technology
to spread vicious lies at the speed of light.

Certain thoughtful observers of pornography in the 1970s asked, of the
scenes in which the vulnerability of women was exploited by offscreen
men, where's the freedom here? The same question can be asked of the
Internet, where important and serious questions including the
oppression of intellectual labor are policed in comically sadistic
terms by the intellectuals of Pharaoh's army.
> --
> nais...@enteract.com
> http://www.naisbodo.com/

Marco S Hyman

unread,
Dec 3, 2000, 3:00:00 AM12/3/00
to
spino...@my-deja.com writes:

> ALSO find good ideas in B school work. If few add to or transmit from
> human knowledge *per se*, their value nonetheless resides in the way
> they enhance people's lives, by, for example, showing them how to
> program in Visual Basic, and thereby earn a living without selling
> drugs. Some of the work done at the private, for-profit University of

Visual Basic: it keeps pushers off the streets!

// marc

Al Dunbar

unread,
Dec 3, 2000, 3:00:00 AM12/3/00
to

<spino...@my-deja.com> wrote in message
news:90ehr2$m12$1...@nnrp1.deja.com...

> In article <90dl73$pc0$1...@news.igs.net>,
> "donald tees" <don...@willmack.com> wrote:
> > spino...@my-deja.com wrote in message <90ckd1$c49
> $1...@nnrp1.deja.com>...
> > >In article
> >
> > >
> > >What you've said illustrates my point that Foucault's theory of
> > >capillary power is relevant to software engineering, for the charge
> of
> > >verbosity is in my observation used by subordinate intellectuals to
> > >discipline threats from source even more subordinate. Strikingly,
> what
> > >attracts it is not only word count and the use of subordinate phrases
> > >but also grammatical accuracy and lack of spelling errors.
> > >
> > >We're all in Pharaoh's army, as Steve McConnell unconsciously knows,
> > >overseen not by Egyptians, but by fellow Israelites whose fear of
> > >Pharaoh wields the whip.
> >
> > I was amused by these paragraphs. The writing is so verbose, it is
> > difficult to tell if it is really a post against pomposity, sarcasm,
> or just
> > amusing.
>
> I should mention at this point that I am a published author, have been
> for about twenty years, and finally that I am under contract to write a
> book on software.

Please let us know when it is available.

> Now, this in itself does not indicate that I am not verbose. The only
> accurate definition of verbosity lies not in raw word count but in the
> RATIO of words to needed and/or original ideas.

OKOK, so you are not verbose. Now tell us what the word is that means that
you are so interested in contemplating the wonderfulness of your own
somewhat voluminous use of the language, that you are willing to sacrifice
almost any opportunity you might have to make your actual meaning clear by
shrouding it in so much double-speak that even those that might otherwise
agree with some of your points are becoming exasperated.

> The problem is that this ratio is not surd, for there is no such thing
> as counting when it comes to ideas. What we count is always the token:
> the expression in words of the idea. This is illustrated by the fact
> that we find that ideas are sometimes equivalent.
>
> The charge of prolixity is all too often technically Fascist since it
> purposely mistakes, for verbosity, a density of new, surprising, anti-
> nominian and otherwise disquieting ideas.

I dount that it is Fascist in this case; most of us just think you use too
many words. Either that, or you are generally incapable of expressing a
single, simple thought, simply (aside from a few quick ripostes). The fact
that we seem unable to express this to you in terms such that you understand
our meaning (rather than the individual meaning of our words) is not our
inability to communicate, IMO, but simply part of your own.

<snip - "I begin to weary of this motif" - Didi, Waiting for Godot (or was
that Gogo?)>

/Al


Al Dunbar

unread,
Dec 3, 2000, 3:00:00 AM12/3/00
to

<spino...@my-deja.com> wrote in message
news:90eiqt$msj$1...@nnrp1.deja.com...

> In article <90cp6u$p5v$1...@bob.news.rcn.net>,
> naisbodo <nais...@enteract.com> wrote:
> > In comp.programming spino...@my-deja.com wrote:

<snip - sigh>

> > This is of course an egregious aggrandizement bolstered by relentless
> > grandiloquence with little substantive justification, and one easily
> > applied back to its framer. Your indictment of his marginalization
> > performatively contradicts itself through self-description; perhaps
> > if your final clause, ostensibly justifying your ad hominem, were
> less
> > nonsequitous it would not so obviously betray its rhetorical nature.
> >

> The difference between you obvious satire is that I have a real social
> and political goal, and where my syntax is complex it is actually
> trying to be fair.

Methinks he is weakening, as evidenced by the obvious grammatical error in
the sentence above :-)

Sorry to the previous poster, as your "obvious satire" was off the mark in
that it made more sense than the matter you were satirizing.

> Your nasty purpose is the opposite, and it is to
> make fun of me.

Not so in the least. This is just good healthy disagreement with some of
your ideas and most of your method.

> I have no personal problem with this for believe it or
> not I do not take myself all that seriously. My concern is that this
> pre-emptive debate about prolixity forestalls any real discussion of
> the ways in which software developers are being materially screwed.

In that case, why do you not start a new thread entitled "the ways in which
software developers are being materially screwed". Perhaps I would discover
more about Steve McConnells book by following that thread, as I have
certainly learned nothing here.

> > If you are not a troll, you will quickly realize the effect of overly
> > formal diction in an informal context. Please, desist in your abuse
> > of formality, and adapt to the groups within which you post. Failure
> > to do so is simply rude.
> >

> No, I will NOT adapt to the group in which I post.

Ergo, he *is* a Troll.

> That is because the
> Internet statistically over-represents the worst elements in our
> society, weighted as it is towards physical cowards, truly pompous neo-
> conservatives, Ku Kluxers, and people like Scientologists and Holocaust
> deniers who use the lack of friction implicit in electronic technology
> to spread vicious lies at the speed of light.

Hey, some of us will agree to some of that, however, trying to change the
statistical balance all on your own by the sheer volume of text is certainly
an onerous task, if an ineffective one.

/Al


Ariel Scolnicov

unread,
Dec 3, 2000, 3:00:00 AM12/3/00
to
spino...@my-deja.com writes:

[...]

> Note the epistemological crisis Al has undergone, for he confessed to a
> vague disquiet. But the crisis is resolved by marginalizing the
> messenger and thus old Al is all relieved, for it's basically harder to
> question institutional power than to marginalize an individual.

Eschew sesquipedilianism!

[...]

--
Ariel Scolnicov

naisbodo

unread,
Dec 3, 2000, 8:49:37 PM12/3/00
to
In comp.programming spino...@my-deja.com wrote:

> The charge of prolixity is all too often technically Fascist

[snip]

> Gresham's law.

No, Godwin's law! :-)

--
nais...@enteract.com
http://www.naisbodo.com/

spino...@my-deja.com

unread,
Dec 3, 2000, 9:06:30 PM12/3/00
to
In article <x7d7f93...@hana.snafu.org>,
Marco S Hyman <ma...@snafu.org> wrote:

> spino...@my-deja.com writes:
>
> > ALSO find good ideas in B school work. If few add to or transmit
from
> > human knowledge *per se*, their value nonetheless resides in the way
> > they enhance people's lives, by, for example, showing them how to
> > program in Visual Basic, and thereby earn a living without selling
> > drugs. Some of the work done at the private, for-profit University
of
>
> Visual Basic: it keeps pushers off the streets!

Note the Foucauldian moment we are enjoying here. I learned Visual
Basic, used it for a number of years, and got a part-time job teaching
VB at an inner city college. A number of my students may very well
have been recovering from joblessness and its attendant misuse of drugs
and alcohol, in the microcosm because they learned VB and became
employable, and in the macrocosm because Clinton's administration
funded training opportunity far more than the previous
admininstrations, did, or the Republicans will after their coup d'etat.

The Foucauldian moment asserts power using pleasure. Therefore, your
slogan trivializes the very real lack of opportunity for inner city
people...and also, through oversimplification, characterises all of
them as pushers, whereas in reality the statistical majority conducts
itself at a personal level better than upper middle class white people,
simply because retribution for "lifestyle experimentation" is so brutal
in the inner city.

This is possibly the major reason why I remain "verbose." 1960s
politics of slogans and bumper stickers turned liberation into friendly
fascism.
>
> // marc

spino...@my-deja.com

unread,
Dec 3, 2000, 9:25:13 PM12/3/00
to
In article <t2lrsvr...@corp.supernews.com>,

"Al Dunbar" <Al_D...@HoTMaiL.com> wrote:>
> > I should mention at this point that I am a published author, have
been
> > for about twenty years, and finally that I am under contract to
write a
> > book on software.
>
> Please let us know when it is available.

It is scheduled for late 2001.


>
> > Now, this in itself does not indicate that I am not verbose. The
only
> > accurate definition of verbosity lies not in raw word count but in
the
> > RATIO of words to needed and/or original ideas.
>

> OKOK, so you are not verbose. Now tell us what the word is that means
that
> you are so interested in contemplating the wonderfulness of your own
> somewhat voluminous use of the language, that you are willing to
sacrifice
> almost any opportunity you might have to make your actual meaning
clear by
> shrouding it in so much double-speak that even those that might
otherwise
> agree with some of your points are becoming exasperated.
>

While I take pleasure in concepts, I am not thrilled with the
wonderfulness of the ideas. They are pessimistic as regards the future.

Look, here are some "simple" ideas: "winning is the only thing"
and "down with intelligence!" You want me to be a modern reductionist
sort of dude who distills the lived complexity of software to a few
simple formula, and I am not gonna. But to sum it up I often quote
Dijkstra. Software is a new form of applied mathematics.


> I dount that it is Fascist in this case; most of us just think you
use too
> many words. Either that, or you are generally incapable of expressing
a
> single, simple thought, simply (aside from a few quick ripostes). The
fact
> that we seem unable to express this to you in terms such that you
understand
> our meaning (rather than the individual meaning of our words) is not
our
> inability to communicate, IMO, but simply part of your own.

Perhaps the problem as you phrase it, Al, has a material basis.
Perhaps so many simple thoughts have been privatized that truly
original thoughts have a genomic or gnomic complexity.

This is really beginning to piss me off, because one of the major
reasons I was as you say verbose was an attempt to be fair to Steve
McConnell, who I briefly met in 1995 and whose book Code Complete is an
excellent piecea work. It's also been an attempt to be fair to other
discussants who may know far more about software engineering than I,
for in many places I've waxed verbose, in saying that the science in
software engineering, to the extent it is science and not power, is
valid.

You may have wanted some strongly worded and simple, manly "flame" of
software engineering like this: "software engineering is a buncha
management jagoffs who are trying to get rid of us Great Programmers
and replace them with underpaid clerks."

The trouble with this simply, manly way of expression is that it
IMMEDIATELY transforms the programmer saying it from his human
complexity into a cartoon character of an unreconstructed, old-
fashioned sort of programmer who resents, sheerly because of his out
dated skill set, anything new. This plays into the software engineer's
hands.

This is a serious fucking matter. Commencing in the 1980s, highly
skilled programmers who were all too willing and able to learn new
technologies were fired less for technical reasons and more for
rhetorical and cultural reasons. At companies like Apple,
management/marketing and programmers adopted almost cartoonishly
opposite rhetorical styles without even thinking: the programmers
dressed and look like lawn trolls: the management and marketing droids
dressed and looked like Brenda Starr.

In American culture, people are subtly encouraged to self-transform
into cartoonlike identities to an extreme extent so that their
personalities fit onto a performance evaluation, but its precisely this
oversimplification of the Self that leads (1) to the layoff of the self-
caricatured lawn troll who insists on using line by line unix, or (2)
the near-ruin of Apple in the early 1990s by out of control Brenda
Starr types.


>
> <snip - "I begin to weary of this motif" - Didi, Waiting for Godot
(or was
> that Gogo?)>
>

Hip weariness is part of the problem for it too manufactures going with
the flow.
> /Al

spino...@my-deja.com

unread,
Dec 3, 2000, 9:42:54 PM12/3/00
to
In article <t2lsipe...@corp.supernews.com>,> > >

> > The difference between you obvious satire is that I have a real
social
> > and political goal, and where my syntax is complex it is actually
> > trying to be fair.
>
> Methinks he is weakening, as evidenced by the obvious grammatical
error in
> the sentence above :-)

The sentence was inapposite but technically correct. "My syntax...was
trying to be fair" is an inapposite contract of "I was using complex
syntax in order to be fair." Inelegantly, and without warning, my
syntax became an active agent that could be said to try, to be fair.
These are unedited, but proofread, posts and I probably should have
spotted this construction.

> > Your nasty purpose is the opposite, and it is to
> > make fun of me.
>
> Not so in the least. This is just good healthy disagreement with some
of
> your ideas and most of your method.

But you haven't gotten at all to the ideas and you haven't been
constructive and you're being MEAN to me :-(. Cut it out or I will
tell Professor Dijkstra :-).

>
> > I have no personal problem with this for believe it or
> > not I do not take myself all that seriously. My concern is that
this
> > pre-emptive debate about prolixity forestalls any real discussion of
> > the ways in which software developers are being materially screwed.
>
> In that case, why do you not start a new thread entitled "the ways in
which
> software developers are being materially screwed". Perhaps I would
discover
> more about Steve McConnells book by following that thread, as I have
> certainly learned nothing here.
>

I've got a fabulous idea. Why don't you just READ his book, or pay me
to write a summary?

> > >
> > No, I will NOT adapt to the group in which I post.
>
> Ergo, he *is* a Troll.

We are having another Foucauldian moment, for it has long been an
article of faith among libertarian digerati that we gots like total
free speech on de Internet now since anybody can say anything. An
implication frequently drawn is that old time liberals and the
Politically Correct do not have our libertarian committment to free
speech because they would materially restrict "hate" speech.

The Foucauldian moment is to apply an apparently pleasurable
description, not to views, but to persons expressing the view. As so
often happens in American culture, the person is in a lighthearted way
reduced to a cartoon: here a hairy gnome who lives under a bridge and
who has a tendency to harass fair maidens.

The Foucauldian moment is to overlay real social injustice with the
laughter of nervous children: for the ORIGINAL origin of the modern use
of "troll" may date from Santa Cruz, CA, in the 1980s.

In that supposedly liberal town, a movement was started against Santa
Cruz "trolls", aging and homeless 1960s hippies who unlike the members
of this NIMBY (Not In My Backyard) movement had not cashed in on the
real-estate boom. Unreflectingly, these "grassroots" yeomen simply
ignored the need for charity and did not reflect that their horror
of "trolls" crystallized their own anxiety about their own (often
foolish and extremely tenuous) financial affairs.

This nasty usage has become virtualized in the appellation "troll", for
many of the Santa Cruz and valley homeowners were also internet
surfers. I hasten to add this is theory and needs empirical
confirmation: but the modern use of "troll" is in my view a form of
hate speech that shows the real shallowness of any committment, on the
internet, to material freedom of speech.


>
> > That is because the
> > Internet statistically over-represents the worst elements in our
> > society, weighted as it is towards physical cowards, truly pompous
neo-
> > conservatives, Ku Kluxers, and people like Scientologists and
Holocaust
> > deniers who use the lack of friction implicit in electronic
technology
> > to spread vicious lies at the speed of light.
>
> Hey, some of us will agree to some of that, however, trying to change
the
> statistical balance all on your own by the sheer volume of text is
certainly
> an onerous task, if an ineffective one.
>

I type fast.

Gene Wirchenko

unread,
Dec 3, 2000, 10:55:48 PM12/3/00
to
spino...@my-deja.com wrote:

[snip]

>I have found that people who are quick with the charge of prolixity use
>it as a timesaver when they simply do not care, for a good reason, a
>bad reason, or no reason at all, to address the issues that were
>raised. You haven't explained the lack of content, and as for critical

Interesting. I've found that people who retreat behind dense
jargon-laden polysyllablism are often trying to hide that they don't
know what they are talking about. Sometimes, they hide their
ignorance from themselves, but are usually less successful in fooling
others.

You'd do much better to put down that thesaurus and write
plainly. It would mean that many more people would be able to
understand you. That is a good thing assuming that your ideas are
worth anyone reading about. Well, are they?

[snip]

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

naisbodo

unread,
Dec 3, 2000, 11:07:03 PM12/3/00
to
[Note to anyone not interested in a verbose rebuttal of Spinoza: stop
reading here, my apologies.]

In comp.programming spino...@my-deja.com wrote:


> Al Dunbar <Al_D...@HoTMaiL.com> wrote:>
>>
>> OKOK, so you are not verbose. Now tell us what the word is that means
>> that you are so interested in contemplating the wonderfulness of your
>> own somewhat voluminous use of the language, that you are willing to
>> sacrifice almost any opportunity you might have to make your actual
>> meaning clear by shrouding it in so much double-speak that even those
>> that might otherwise> agree with some of your points are becoming
>> exasperated.
>
> While I take pleasure in concepts, I am not thrilled with the
> wonderfulness of the ideas. They are pessimistic as regards the future.

This bit of verbiage lacks context. "The" ideas? Which ideas do you
mean? "Concepts"? Which concepts do you mean? This didn't answer his
post at all! Luckily, you went on to give some more relevant text:

> Look, here are some "simple" ideas: "winning is the only thing"
> and "down with intelligence!" You want me to be a modern reductionist
> sort of dude who distills the lived complexity of software to a few
> simple formula, and I am not gonna.

Yikes! You're indulging in two fallacies to make your point. Allow
me to enumerate my arguments for clarity:

First, you unnecessarily create a link between complexity of expression
and complexity of thought. Complex thoughts can be expressed in simple
ways, and simple thoughts can be expressed in complex ways. In order
to express complex ideas simply, however, one must have a clear grasp
of them.

So why does the realm of academia insist on using "big words" if they
can do without? Obviously, because expression is made more concise
using these words. This is desirable because it reduces the level
of redundancy in communication, which is high in a specific field if
one is reduced to simple speech. Having a handy label for an idea
lets you express it without taking the time to explain it. (See my
third point for the disadvantage to this.)

Now, once you move outside this realm in which everyone understands
the more concise expression of these ideas, simply because they may
not be familiar with them or may not know the academic labels, it no
longer reduces redundancy in communication, because the ideas are not
commonly expressed. Therefore it behooves the speaker to reduce his
*expression* to simple forms, even if they are more verbose, when in
a context where the labels and more concise expressions are unlikely
to be understood.

That is to say, you're unnecessarily claiming that you cannot express
your ideas more simply without reducing the complexity of the ideas
themselves. Complexity of expression and complexity of thought are
two separate measures, and your failure to distinguish them is what
I have labeled your first fallacy.

Second, you're using the rhetorical tactic of reducto ad absurdum in
your examples:

> Look, here are some "simple" ideas: "winning is the only thing"
> and "down with intelligence!"

Even if the above complexities *were* inseparable, this style of
argumentation would be flawed. Reducto ad absurdum disproves only
the worst possible case, because the ability to contrive a particular
example which is obviously flawed does not imply the ability to infer
anything about the entire set of cases. However, it's a common bit
of rhetoric, despite its flaws; I suggest you avoid it in the future,
if you are serious about persuading logical-thinking people rather
than merely those who are easily impressionable.

To attack it from a discursive rather than logical standpoint, look
at your example as one end of a spectrum (simple ideas) versus your
normal level of expression as the other (complex ideas). There are
a number of shades of grey between these two extremes which your
argument tacitly dismisses. I'm sure you're familiar with the
deconstruction of false dichotomies such as this, so I'll leave
it to you to determine the consequences of the above.

Third and finally, your use of labels does more harm than good. You
only communicate your purpose to those who have already taken the time
to understand the ideas expressed by your labels, when the ideas they
describe are only uncommonly known in the context in which you use them.
Because of this, you do little good, but this alone does not make your
use of them harmful; however, you abuse labels:

>>> [...] Fascist [...]

Do read about Godwin's law sometime. Your abuse definitely overstates
your ideas. Regardless of their basic correctness, throwing around
words like "Fascist" implies they have a different magnitude of
importance than they actually do. When you express all of your ideas
with this extreme level, your words cease have any sense of proportion
and one is not sure how seriously to take *any* of your ideas, since
relative to one another they're all roughly the same. What's worse,
many of your ideas aren't intended seriously (the insults as the most
obvious example), which needlessly reduces your own ability to express
your ideas to others.

What is the end result of all of this? You've completely failed to
communicate, sir, and if you'd realize that your ideas can be simply
expressed without reducing their complexity, take the time to put them
in terms people can grasp more easily, and put things in context rather
than aggrandizing each argument on a scale where they all become quite
meaningless, you'd be able to communicate more effectively. Failure to
comply with the above will be taken as an acknowledgment that you're
simply not seriously interested in communication.

And, of course, if you are not interested in communication, then do not
expect me to read your posts. This is your pre-plonk warning. Please
take heed.

--
nais...@enteract.com
http://www.naisbodo.com/

spino...@my-deja.com

unread,
Dec 4, 2000, 1:32:07 AM12/4/00
to
In article <90f597$o4a$1...@bob.news.rcn.net>,

naisbodo <nais...@enteract.com> wrote:>
> This bit of verbiage lacks context. "The" ideas? Which ideas do you
> mean? "Concepts"? Which concepts do you mean? This didn't answer
his
> post at all! Luckily, you went on to give some more relevant text:
>
> > Look, here are some "simple" ideas: "winning is the only thing"
> > and "down with intelligence!" You want me to be a modern
reductionist
> > sort of dude who distills the lived complexity of software to a few
> > simple formula, and I am not gonna.
>
> Yikes! You're indulging in two fallacies to make your point. Allow
> me to enumerate my arguments for clarity:
>
> First, you unnecessarily create a link between complexity of
expression
> and complexity of thought. Complex thoughts can be expressed in
simple
> ways, and simple thoughts can be expressed in complex ways. In order
> to express complex ideas simply, however, one must have a clear grasp
> of them.
>
This is certainly no law. Like some of Steve's saws it seems to have
authority and generality but that very authority and generality is
undercut by simple counterexamples.

To be brutal, it is not true that any complex thought can be expressed
simply. Ironically, we all accept this as regards science and
mathematics but seem to feel that this does not apply to the humanities
and software engineering.

Shakespeare's plays often express complex thoughts about personality
and human relationships, and his vocabulary was large and likewise his
sentence structure.

Your "simplicity" is a psychological, reader-response predicate which
is an attribute of the reader's reception.

> So why does the realm of academia insist on using "big words" if they
> can do without? Obviously, because expression is made more concise
> using these words. This is desirable because it reduces the level
> of redundancy in communication, which is high in a specific field if
> one is reduced to simple speech. Having a handy label for an idea
> lets you express it without taking the time to explain it. (See my
> third point for the disadvantage to this.)
>
> Now, once you move outside this realm in which everyone understands
> the more concise expression of these ideas, simply because they may
> not be familiar with them or may not know the academic labels, it no
> longer reduces redundancy in communication, because the ideas are not
> commonly expressed. Therefore it behooves the speaker to reduce his
> *expression* to simple forms, even if they are more verbose, when in
> a context where the labels and more concise expressions are unlikely
> to be understood.
>

Sounds like you've neatly made my thoughts inexpressible which as I
have said is the goal of the Foucauldian system: by seemingly
pleasurable means, to make certain thoughts not formulable.

For if you reduce the word count by allowing what you call big words
and what I call terms of art, the writer is under the charge of using
big words and terms of art. If you prohibit the big words, the writer
is charged with verbosity. His thoughts (including his desire for
charity and nuance) are at times conveniently silenced.

> That is to say, you're unnecessarily claiming that you cannot express
> your ideas more simply without reducing the complexity of the ideas
> themselves. Complexity of expression and complexity of thought are
> two separate measures, and your failure to distinguish them is what
> I have labeled your first fallacy.
>

This is a REAL example of impressive-sounding bullshit which truly is
prolix for there is a low "ratio" of words...to true ideas.

For in no final sense can we speak of "measuring complexity" although
software engineers talk as if this is a given. Thought precedes
numeration and therefore to measure complexity is deep nonsense.

This was seen in the early days of software engineering when lines of
code were used as a metric.

"Measuring complexity" is reification for it makes a thing out of a
concept which exists primarily in a network of concepts. It also
allows the measurer's personal bias to be presented as Science.

> Second, you're using the rhetorical tactic of reducto ad absurdum in
> your examples:

"Reductio ad absurdam" (the correct spelling) is not a rhetorical
tactic, it is a valid logical method.

>
> > Look, here are some "simple" ideas: "winning is the only thing"
> > and "down with intelligence!"
>
> Even if the above complexities *were* inseparable, this style of
> argumentation would be flawed. Reducto ad absurdum disproves only
> the worst possible case, because the ability to contrive a particular
> example which is obviously flawed does not imply the ability to infer
> anything about the entire set of cases. However, it's a common bit
> of rhetoric, despite its flaws; I suggest you avoid it in the future,
> if you are serious about persuading logical-thinking people rather
> than merely those who are easily impressionable.

Let me help you out. You're struggling to think, not of the valid
technique of reductio but of the strawman argument.

I was not of course claiming that overemphasis on content-free
simplicity led either to the football Fascism of Vince Lombardi or the
authoritarianism of Franco. This would be a strawman argument.

Instead, I was hoping to form a picture in the reader's mind of the way
authoritarian societies including the modern corporation use anti-
intellectualism to discipline the intellectuals they are forced to hire
to run a technological society. In actuality and from a fiduciary
standpoint, their conduct is perfectly rational: no corporation wants
to let scientists and intellectuals sit around and think about stuff in
general.

But the scientists and intellectuals have in my view a responsibility
(even from the standpoint of their position as employees) to see that
their interests do not coincide with the fiduciary interests of the
firm.

Software developers are employed, in our society, at will. They may as
well realize for their own sanity that yes indeed they are interested
in software for its own sake. Software is fun, software is cool, and
knowing a lot about it may not get you hot chicks but at least keeps
you from being homeless in a basically "fuck you", laissez-faire world.

Software developers therefore have a real interest in working at the
edge of their capabilities which varies at times from the most
effective use of their skills: many firms deliberately hire developers
who are overqualified for the tasks the firm has in mind, promising
(for example) Java work while requiring Cobol work after the
interview. This is sleazy but it shows that developers have
professional interests that do not coincide with fiduciary interests.

In law and in ethics, there is nothing wrong with this. Part of being
an employed adult in a company is putting at least some of your
ambitions on hold, and reconciling them with the goals of the firm.

But parts of software engineering pretend that there is absolutely no
space between the employee's interests and those of the firm, and that
the employee WANTS to be deskilled. This is to me the real reason for
the at times Fascistic insistence on defeating real complexity found in
software engineering rhetoric, for Fascism as a movement is based on
people having no divergent interests from those of the state (or
corporation) and also on a pessismism about mastering the complexity of
negotiating divergent interests of different classes of people.

>
> To attack it from a discursive rather than logical standpoint, look
> at your example as one end of a spectrum (simple ideas) versus your
> normal level of expression as the other (complex ideas). There are
> a number of shades of grey between these two extremes which your
> argument tacitly dismisses. I'm sure you're familiar with the
> deconstruction of false dichotomies such as this, so I'll leave
> it to you to determine the consequences of the above.
>

The problem here is that there is usually no warning, in the form of
gradually darker shades of grey, when authoritarianism appears on the
scene. Brutality has as part of its strategy the element of surprise,
as in Kristallnacht, when German Jews were completely surprised by the
overnight barbarism of their neighbors.

Corporations are not Fascistic states but many corporations are too
authoritarian for their own good (as in the case where work-to-rule
trumps productivity.) I think we need as developers a way, other than
the cyberpunk way, of speaking to power. The cyberpunk way to to
undercut through a higher knowledge of technology. The more human way
would be to be able to address, in a civilised fashion, the socially
repressive elements of technology.

For example, for every 100 developers willing to ignore standards and
to deliberately place logic bombs in their code in order to maintain
their position, there is 1 or fewer Ellen Ullmans. Ullman, the author
of Close to the Machine, a book about being a programmer, simply
refused a client's request that she insert keystroke monitoring in a
routine the client had requested because Ellen did not believe workers
should be subject to keystroke monitoring. I happen to disagree with
her view (I think a keystroke monitor could be employee friendly since
it could allow the employee to create macros) but note that Ellen
simply spoke up instead of trying to evade the issue like a
cyberpunkette.

> Third and finally, your use of labels does more harm than good. You
> only communicate your purpose to those who have already taken the time
> to understand the ideas expressed by your labels, when the ideas they
> describe are only uncommonly known in the context in which you use
them.
> Because of this, you do little good, but this alone does not make your
> use of them harmful; however, you abuse labels:
>
> >>> [...] Fascist [...]
>

The label "Fascist" has turned into a sort of verbal stinkbomb but note
that I, in my wordy way, talked of tendencies towards authoritarianism
which at moments of crisis do become Fascist.

My understanding of Fascism is not based on Spielberg's movies but
instead on research on "The Authoritarian Personality" performed by
Theodore Adorno in the 1940s. Adorno's thesis was that in societies in
economic crisis (such as Weimar Germany) working and middle class
support for Fascism grows out of people's personal tendencies to
internalize superego commands AT VARIANCE from their desires.

In corporations in economic crisis, people internalize authority
without resolving the personal conflicts they create. In our business,
they work absurd hours without really wanting to, and they take out the
anger on easy targets, such as that bozo who wrote that program you're
trying to fix. This is safer than questioning whether the program
needs to be rewritten, in somewhat the same way it was safer to elect
Hitler than to call for true economic reform of Germany after WWI.

> Do read about Godwin's law sometime. Your abuse definitely overstates
> your ideas. Regardless of their basic correctness, throwing around
> words like "Fascist" implies they have a different magnitude of
> importance than they actually do. When you express all of your ideas
> with this extreme level, your words cease have any sense of proportion
> and one is not sure how seriously to take *any* of your ideas, since
> relative to one another they're all roughly the same. What's worse,
> many of your ideas aren't intended seriously (the insults as the most
> obvious example), which needlessly reduces your own ability to express
> your ideas to others.
>

I haven't called Steve McConnell a fascist, at all, and he probably
scores low on Adorno's authoritarianism scale. I've used the word in a
completely different context, and it is as if the word was not properly
parsed, but seen as a hot-button or keyword. This, basically, is not
my problem, for the seriousness of labor problems in our industry
(including divorce and suicide) warrants calling a spade a spade.

You're essentially trying to persuade me to rejoin the problem set, of
people who phrase false notions in a digestible form. As I've said, I
did not dare put this into expression when my kids were young and I
know the dangers of expressing them.

One thing I have noticed. When someone sets off a stinkbomb such as
the truth in a project heading for disaster, he is usually not a
popular kinda guy. My hero Dijkstra, after all, was sidelined after he
spoke the truth about PL/I and software engineering.

Part of the problem set is the very metaphor "the marketplace of
ideas." I sell my labor: I do not try to sell my ideas.

> What is the end result of all of this? You've completely failed to
> communicate, sir, and if you'd realize that your ideas can be simply
> expressed without reducing their complexity, take the time to put them
> in terms people can grasp more easily, and put things in context
rather
> than aggrandizing each argument on a scale where they all become quite
> meaningless, you'd be able to communicate more effectively. Failure
to
> comply with the above will be taken as an acknowledgment that you're
> simply not seriously interested in communication.

"People" is the interesting word here, for it reifies the notion of the
statistical mean. I am not speaking to dots on a chart. I am speaking
to persons, to perhaps the one guy (or hopefully, hot chick) who gets
it.

>
> And, of course, if you are not interested in communication, then do
not
> expect me to read your posts. This is your pre-plonk warning. Please
> take heed.

The more people, who waste my time with pretentious discussions of
literary style, who *plonk* me, the better.

spino...@my-deja.com

unread,
Dec 4, 2000, 1:44:16 AM12/4/00
to
In article <3a2b1379...@news.shuswap.net>,

ge...@shuswap.net wrote:
> spino...@my-deja.com wrote:
>
> [snip]
>
> >I have found that people who are quick with the charge of prolixity
use
> >it as a timesaver when they simply do not care, for a good reason, a
> >bad reason, or no reason at all, to address the issues that were
> >raised. You haven't explained the lack of content, and as for
critical
>
> Interesting. I've found that people who retreat behind dense
> jargon-laden polysyllablism are often trying to hide that they don't
> know what they are talking about. Sometimes, they hide their
> ignorance from themselves, but are usually less successful in fooling
> others.

Gee, my experience in programming is quite the opposite. If you can
say "This module does this", accurately, using as many words as it
takes, you know more than the inarticulate bozo who just codes.

It is TRUE that great modules are what Ed Yourdon calls functionally
bound and that as a result, their description is a simple
sentence: "calculate the square root of the input number."

But note, of course, that Yourdon's taxonomy of binding had to admit
other levels, and that in the REAL world, the writing that accurately
describes the function of a module is more complex: "this module reads
the FOO record set and deletes all noncurrent records."

The real problems occur not when the commenter or presenter is overly
verbally facile (although the folk myth in data processing, based on
social inequality but unspeakable as such, is indeed that all overly
facile presenters are bullshitters.) It occurs when the program
comments have no relation to each other ("this module advances the
printer and also makes coffee") and when the presenter stumbles and is
reduced to silence.

>
> You'd do much better to put down that thesaurus and write
> plainly. It would mean that many more people would be able to
> understand you. That is a good thing assuming that your ideas are
> worth anyone reading about. Well, are they?
>

You assume that I'm using a thesaurus and you cannot admit that *le mot
juste* just occurs to me...after a 16 hour day coding Visual Basic
(this, by the way, is the truth.) This is to have a downsized view of
human abilities which is part of the problem set. Perhaps I am a
monster: a recent employer described me as "Ed, the technical monster"
in a brochure. Perhaps I am a Cartesian evil genius, but as far as I
can tell, I am an ordinary slob who doesn't get laid a lot, and
sublimates like a Good Boy. Would you rather I was a sex addict?

> [snip]
>
> Sincerely,
>
> Gene Wirchenko
>
> Computerese Irregular Verb Conjugation:
> I have preferences.
> You have biases.
> He/She has prejudices.
>

spino...@my-deja.com

unread,
Dec 4, 2000, 1:58:47 AM12/4/00
to
In article <t2latec...@corp.supernews.com>,

"Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
>
> In deference to Mr. Gilb, whose works I have not read, I would assume
that
> his "high class phraseology" was combined with actual content, rather
than
> simply being there for its own sake.
>
Yeah, it was. He gave techniques that I put to use for defaulting
fields in a humanistic fashion. He assumed that the programmer would
be able to spend time on this.

However, part of the problem with software engineering is that it is
used to "discipline" programmers into writing just the code the
designers think is necessary. Despite all their talk about "the user",
the designers do not mean the actual computer operator. They mean the
owners of the firm, who typically don't give a rat's ass that their
input operators have carpal tunnel syndrome from entering common
defaults.

Humanized input would have avoided, for example, the problems in the
Florida recount. An intelligent programmer of an electronic voting
machine would have displayed a message saying "are you sure you want to
vote for TWO candidates?" but note that under rigid software
engineering discipline, our boy would have been handed a set of
rigid "specs", and (because the so-called architects had hogged most of
the development time making pretty charts in Visio) our boy would not
have the time to consider the problem of illogical input.

The "software engineering" vision is after all one of dividing task
planning from execution in an area, that of software development, where
this division often makes no sense. Software engineering seems to
systematically ignore the fact that the intelligent programmer is
uniquely positioned to see marginal cases (such as caused the Florida
mess.) But by taking the real rationality (of planning a task and then
executing it) and fetishizing and reifying it, software engineering
does cause more problems than it solves.

I'd suggest, Al, that reading some of the texts might help your case,
and that part of my verbosity is simply a density of references.

> > I am somewhat arrogantly trying to give a name and form to what I
have
>
> "somewhat"? :-)
>
> > seen as success in software development and universally it seems to
me
> > that software is most successful when it is critical, human, pro-
labor,
> > compassionate. Of course, I do not mean financial success,
> > necessarily. I mean instead a holistic success in which NO
> > stakeholder, including the programmers, pay for the success with
> > exhaustion, broken marriages, and other tragedies.
>
> Sorry, but, on this point at least, I will have to AGREE with you. I
would
> bet, however, that many of those people whose lives you want to
protect from
> abuse perpetrated on them by the establishment would get not much
more than
> a good laugh out of your verbose rants on their behalf. You would
likely say
> that that is because they are not your philosophical equal. To that I
say I
> am glad.
>

We don't need no namby pamby stinkin do-gooder elitists to help us out.

>
> Actually, I do not feel that way. I have often suspected your
inability to
> understand what others say; it appears that sarcasm is just one more
thing
> you have difficulty discerning. :-)
>
> > I am not a Turing experiment although I am
> > almost as weird as Turing was.
>
> This fact has been made abundantly clear.

I'm not gay, although there's nothing wrong with that :-).
>
> /Al
>
> > > <snip - we have already seen enough of this>

Al Dunbar

unread,
Dec 4, 2000, 2:14:14 AM12/4/00
to

<spino...@my-deja.com> wrote in message
news:90eu74$v64$1...@nnrp1.deja.com...

> In article <x7d7f93...@hana.snafu.org>,
> Marco S Hyman <ma...@snafu.org> wrote:
> > spino...@my-deja.com writes:
> >

<snip>

> This is possibly the major reason why I remain "verbose."

I thought you remained verbose in order to disprove our assertion that you
were verbose, a statement that you took exception to some posts ago.

/Al

Al Dunbar

unread,
Dec 4, 2000, 2:14:52 AM12/4/00
to

<spino...@my-deja.com> wrote in message
news:90f0bd$sj$1...@nnrp1.deja.com...

> In article <t2lsipe...@corp.supernews.com>,> > >
> > > The difference between you obvious satire is that I have a real
> social
> > > and political goal, and where my syntax is complex it is actually
> > > trying to be fair.
> >
> > Methinks he is weakening, as evidenced by the obvious grammatical
> error in
> > the sentence above :-)
>
> The sentence was inapposite but technically correct.

No it wasn't. Granted that the "you obvious satire" was a typo for "youR
obvious satire", it still behooves you when referring to the "difference
between" to have two things between which there is a difference, not just
one thing. Extrapolating from the partial sentence, I assume that you really
meant to say something along the lines of:

"The difference between youR obvious satire AND MY MUCH MORE BRILLIANT
DISCOURSIVE STYLE is that I have a real social and political goal, and where


my syntax is complex it is actually trying to be fair."

<snip - when will this all end?>

> > > I have no personal problem with this for believe it or
> > > not I do not take myself all that seriously. My concern is that
> this
> > > pre-emptive debate about prolixity forestalls any real discussion of
> > > the ways in which software developers are being materially screwed.
> >
> > In that case, why do you not start a new thread entitled "the ways in
> which
> > software developers are being materially screwed". Perhaps I would
> discover
> > more about Steve McConnells book by following that thread, as I have
> > certainly learned nothing here.
> >
> I've got a fabulous idea. Why don't you just READ his book, or pay me
> to write a summary?

Read maybe; pay you, not likely. How could I be sure of getting value for
money based on the extent of my knowledge about your writing style? Also,
your summary is sure to vastly exceed the original in volume, whether
measured in pages, words, concepts, or the time it takes to wade through it.

> > > >
> > > No, I will NOT adapt to the group in which I post.
> >
> > Ergo, he *is* a Troll.
>
> We are having another Foucauldian moment, for it has long been an
> article of faith among libertarian digerati that we gots like total
> free speech on de Internet now since anybody can say anything. An
> implication frequently drawn is that old time liberals and the
> Politically Correct do not have our libertarian committment to free
> speech because they would materially restrict "hate" speech.
>
> The Foucauldian moment is to apply an apparently pleasurable
> description, not to views, but to persons expressing the view. As so
> often happens in American culture, the person is in a lighthearted way
> reduced to a cartoon: here a hairy gnome who lives under a bridge and
> who has a tendency to harass fair maidens.

If anyone has reduced you to a cartoon, it is not me. Mind you, you also
tried the same trick against me a few posts back ("go back to your
Dilbertized..."). I take it from this that you are not much different in
substance from that which you rail against.

> > > That is because the
> > > Internet statistically over-represents the worst elements in our
> > > society, weighted as it is towards physical cowards, truly pompous
> neo-
> > > conservatives, Ku Kluxers, and people like Scientologists and
> Holocaust
> > > deniers who use the lack of friction implicit in electronic
> technology
> > > to spread vicious lies at the speed of light.
> >
> > Hey, some of us will agree to some of that, however, trying to change
> the
> > statistical balance all on your own by the sheer volume of text is
> certainly
> > an onerous task, if an ineffective one.
> >
> I type fast.

...and it shows.

/Al

Heinz W. Wiggeshoff

unread,
Dec 4, 2000, 2:34:30 AM12/4/00
to
Ariel Scolnicov (ari...@compugen.co.il) writes:
>
> Eschew sesquipedilianism!

Thank you for that new addition to my Scrabble word list.
Of course, I'll be playing with two letter racks now.

(If this stupid thread doesn't die soon, no harm in making it
amusing, right?)

Al Dunbar

unread,
Dec 4, 2000, 2:35:44 AM12/4/00
to

<spino...@my-deja.com> wrote in message
news:90eva5$2k$1...@nnrp1.deja.com...

> In article <t2lrsvr...@corp.supernews.com>,
> "Al Dunbar" <Al_D...@HoTMaiL.com> wrote:>

<snip - please pass the scissors sharpener!>

> > > Now, this in itself does not indicate that I am not verbose. The
> only
> > > accurate definition of verbosity lies not in raw word count but in
> the
> > > RATIO of words to needed and/or original ideas.
> >
> > OKOK, so you are not verbose. Now tell us what the word is that means
> that
> > you are so interested in contemplating the wonderfulness of your own
> > somewhat voluminous use of the language, that you are willing to
> sacrifice
> > almost any opportunity you might have to make your actual meaning
> clear by
> > shrouding it in so much double-speak that even those that might
> otherwise

> > agree with some of your points are becoming exasperated????


> >
> While I take pleasure in concepts, I am not thrilled with the
> wonderfulness of the ideas. They are pessimistic as regards the future.

As was I regarding the likelihood that you could answer a simple question
either simply or in your usual style. Maybe that is because I forgot the
question mark. Look up and you will see four of them.

> This is really beginning to piss me off, because one of the major
> reasons I was as you say verbose was an attempt to be fair to Steve
> McConnell, who I briefly met in 1995 and whose book Code Complete is an
> excellent piecea work.

This must be the height of irony! You recognizing "Code Complete" as an
excellent piece of work, when it is so well crafted that it accurately
conveys the author's ideas using the most straightforward and approachable
style imaginable.

<snip>

> This is a serious fucking matter. Commencing in the 1980s, highly
> skilled programmers who were all too willing and able to learn new
> technologies were fired less for technical reasons and more for
> rhetorical and cultural reasons.

I think it is time someone called you on your unsubstantiated statements.
Name one person that was fired in the manner stated, and/or provide some
documentation to indicate that this was indeed the case.

> > <snip - "I begin to weary of this motif" - Didi, Waiting for Godot
> (or was
> > that Gogo?)>
> >
> Hip weariness is part of the problem for it too manufactures going with
> the flow.

Is it possible that we could say anything that did not somehow only confirm
your beliefs in some manner without your even having to agree with us?

Al Dunbar

unread,
Dec 4, 2000, 2:51:48 AM12/4/00
to

<spino...@my-deja.com> wrote in message
news:90fdp8$aen$1...@nnrp1.deja.com...

> In article <90f597$o4a$1...@bob.news.rcn.net>,
> naisbodo <nais...@enteract.com> wrote:>

<snip>

> I was not of course claiming that overemphasis on content-free
> simplicity led either to the football Fascism of Vince Lombardi or the
> authoritarianism of Franco. This would be a strawman argument.
>
> Instead, I was hoping to form a picture in the reader's mind of the way
> authoritarian societies including the modern corporation use anti-
> intellectualism to discipline the intellectuals they are forced to hire
> to run a technological society.

Unfortunately, I think the consensus is that you have not succeeded in your
attempt.

<snip>

> You're essentially trying to persuade me to rejoin the problem set, of
> people who phrase false notions in a digestible form.

No. We would prefer you to stop phrasing possibly true notions in an
essentially indigestible form.

> As I've said, I
> did not dare put this into expression when my kids were young and I
> know the dangers of expressing them.

Hmmmm... you were trying to protect your kids from a flame war?

/Al

naisbodo

unread,
Dec 4, 2000, 2:54:59 AM12/4/00
to
In comp.programming spino...@my-deja.com wrote:

> The more people, who waste my time

Waste *your* time??? I spent quite a bit of time trying to prepare a
carefully reasoned reply to satisfy your requirements to discuss matters
at *your* level, going out of my way even though you're being completely
rude and irresponsible in the group.

If you thought *I* was wasting your time, put yourself in my shoes or
anyone else's. You might realize that it's a good idea to take a few
years off of Usenet and stop wasting everyone *else's* time with your
bullshit.

> with pretentious

Who are *you* to call anyone pretentious? If someone asks you to speak
on their level, you spew bullshit at them. If someone responds to you
on your own level, you spew bullshit at them. Get a clue, anyone can
get a book published--it doesn't mean you know what you're talking
about, no matter how good you are at name dropping.

> who *plonk* me, the better.

Since you obviously have no intent of communicating with anyone, let
alone a "hot chick" (You realize that's offensive to some of us?), you
leave no choice on this one.

I naively thought you might have pure motives, and that you were having
serious issues in your attempts to communicate, which I might be able to
help you resolve through a bit of logical discussion. You've allowed me
to thoroughly establish that this is not the case, and in fact, you are
a troll and you care nothing for discussion, at any level.

This is, I hope, valuable to anyone else who might have been unsure as to
whether or not you were simply trolling. The more people who plonk you,
the better. Much better for them if they haven't wasted their own
precious time attempting to communicate with you.

*plonk*

Flamingly yours,

--
nais...@enteract.com
http://www.naisbodo.com/

Al Dunbar

unread,
Dec 4, 2000, 2:58:01 AM12/4/00
to

<spino...@my-deja.com> wrote in message
news:90feg0$b23$1...@nnrp1.deja.com...

> In article <3a2b1379...@news.shuswap.net>,
> ge...@shuswap.net wrote:
> > spino...@my-deja.com wrote:
> >
> > [snip]
> >

<snip>

> > You'd do much better to put down that thesaurus and write
> > plainly. It would mean that many more people would be able to
> > understand you. That is a good thing assuming that your ideas are
> > worth anyone reading about. Well, are they?
> >
> You assume that I'm using a thesaurus and you cannot admit that *le mot
> juste* just occurs to me...after a 16 hour day coding Visual Basic
> (this, by the way, is the truth.)

Gene's thesaurus comment was purely allegorical. We all know that if you
truly used a thesaurus you might make more sense.

> This is to have a downsized view of
> human abilities which is part of the problem set. Perhaps I am a
> monster: a recent employer described me as "Ed, the technical monster"
> in a brochure. Perhaps I am a Cartesian evil genius, but as far as I
> can tell, I am an ordinary slob who doesn't get laid a lot,

So much for your theory that your style of language is a chick magnet.

/Al


Al Dunbar

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to

<spino...@my-deja.com> wrote in message
news:90ffb6$bgf$1...@nnrp1.deja.com...

> In article <t2latec...@corp.supernews.com>,
> "Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
> >
> > In deference to Mr. Gilb, whose works I have not read, I would assume
> that
> > his "high class phraseology" was combined with actual content, rather
> than
> > simply being there for its own sake.
> >
> Yeah, it was. He gave techniques that I put to use for defaulting
> fields in a humanistic fashion.

Well, in that case, you almost seem to be agreeing with me on the nature of
the difference between his "high class phraseology" and your own. Either
that, or you are once again failing to understand the implications of a
simple statement.

> I'd suggest, Al, that reading some of the texts might help your case,
> and that part of my verbosity is simply a density of references.

Exactly. It is as if you cannot speak directly on your own, but need to
constantly make references to various philosophers and others in the
mistaken belief that this will impress the fight out of the opposition.

<snip>

> > > I am not a Turing experiment although I am
> > > almost as weird as Turing was.
> >
> > This fact has been made abundantly clear.
>
> I'm not gay, although there's nothing wrong with that :-).

Ahh, now we are having a Seinfeldian moment, are we?

/Al


Richard Heathfield

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to
spino...@my-deja.com wrote:
>
> In article <90f597$o4a$1...@bob.news.rcn.net>,
> naisbodo <nais...@enteract.com> wrote:>
<snip>

> >
> > Yikes! You're indulging in two fallacies to make your point. Allow
> > me to enumerate my arguments for clarity:
> >
> > First, you unnecessarily create a link between complexity of
> expression
> > and complexity of thought. Complex thoughts can be expressed in
> simple
> > ways, and simple thoughts can be expressed in complex ways. In order
> > to express complex ideas simply, however, one must have a clear grasp
> > of them.

Let's read this quotation very carefully before we continue - naisbodo
has not said "all complex thoughts can be expressed in simple ways". The
statement "complex thoughts can be expressed in simple ways" is mildly
ambiguous, but a well-balanced person would conclude that naisbodo is
not trying to propose that 100% of complex thoughts can be expressed
simply, for the simple reason that such an attempt would be vulnerable
to a single counter-example, and naisbodo is not dumb enough to open
himself up to such an accusation unless he knows he can support it. In
this case, the "implied all" case is insupportable, so I assume he meant
the "implied some" case.

> >
> This is certainly no law. Like some of Steve's saws it seems to have
> authority and generality but that very authority and generality is
> undercut by simple counterexamples.
>
> To be brutal, it is not true that any complex thought can be expressed
> simply.

It is true, however, that some complex thoughts can be expressed simply.
You are trying to extend naisbodo's position to a point where it can be
defeated - in other words, you're "setting up a strawman".


> Ironically, we all accept this as regards science and
> mathematics

Simple examples of complex thought which can be expressed simply:

F = ma (from Newtonian mechanics)
E = mcc (from relativity theory - sorry for the absence of
subscripts...)

> but seem to feel that this does not apply to the humanities
> and software engineering.

Since you're talking about software engineering, I might as well point
out that the IOCCC is a marvellous example of how *simple* thoughts can
be expressed in a *complex* way.

>
> Shakespeare's plays often express complex thoughts about personality
> and human relationships, and his vocabulary was large and likewise his
> sentence structure.

Sure. So?

>
> Your "simplicity" is a psychological, reader-response predicate which
> is an attribute of the reader's reception.

How do you know that? Perhaps his simplicity is just simple.

Defining simplicity is actually an alarmingly complex activity!

<snip>

> For if you reduce the word count by allowing what you call big words
> and what I call terms of art, the writer is under the charge of using
> big words and terms of art. If you prohibit the big words, the writer
> is charged with verbosity. His thoughts (including his desire for
> charity and nuance) are at times conveniently silenced.

There's a place to use big words, and that place is in a forum and
context where everyone likely to read or hear those words is likely to
garner your intended meaning, and where communication is more effective
because of the bigness of the words.

There's a place to use little words, and that place is in a forum and
context where the bigger words would confuse a significant proportion of
your audience or readership. In this case, the forum is
comp.programming, a technical discussion newsgroup (always re-read
before posting! - I note that this is cross-posted to two newsgroups
with which I am unfamiliar, alt.folklore.computers and comp.software-eng
- so I don't know whether my point is valid in those newsgroups), but
the context has little or nothing to do with the technical side of
programming. Therefore, leaving topicality issues aside for the moment,
little words are appropriate. Those big words which don't enjoy wide
understanding within the programming community which this newsgroup (or
these newsgroups!) represents should either be defined as you go or
eschewed (rejected) altogether.

>
> > That is to say, you're unnecessarily claiming that you cannot express
> > your ideas more simply without reducing the complexity of the ideas
> > themselves. Complexity of expression and complexity of thought are
> > two separate measures, and your failure to distinguish them is what
> > I have labeled your first fallacy.
> >
> This is a REAL example of impressive-sounding bullshit which truly is
> prolix for there is a low "ratio" of words...to true ideas.

Not really. It's possible to call a spade a manually operated
agricultural excavation implement, and it's possible to summarise the
complex behaviour of a body in a gravitational field with a simple
equation. Therefore, examples exist which show that it is possible for
complexity of expression to be unrelated to complexity of thought, and
therefore they are separate measures. Therefore, he is correct.

>
> For in no final sense can we speak of "measuring complexity" although
> software engineers talk as if this is a given. Thought precedes
> numeration and therefore to measure complexity is deep nonsense.

To measure complexity objectively is difficult, if not impossible. To
measure it heuristically and subjectively is something most people
reading this newsgroup will do on most days. Hardly nonsense.

>
> This was seen in the early days of software engineering when lines of
> code were used as a metric.

It was not foolish to seek to measure software complexity. It is foolish
to use lines of code as your sole metric. We "know" intuitively that a
10,000,000 line program is more complex than a 10 line program. What we
can't know is that a 2,000 line program is more complex than a 1,000
line program.


> "Measuring complexity" is reification for it makes a thing out of a
> concept which exists primarily in a network of concepts. It also
> allows the measurer's personal bias to be presented as Science.

Measuring complexity is something we do every day. The fact that we
can't measure it with a ruler or a balance is neither here nor there -
we make heuristic judgements of complexity regularly. Sometimes,
therefore, we make wrong judgements. But we get it right often enough
that we consider it worth continuing to do.

>
> > Second, you're using the rhetorical tactic of reducto ad absurdum in
> > your examples:
>
> "Reductio ad absurdam" (the correct spelling)

The Web is not known for its devotion to accuracy. Nevertheless, here
are some Web search findings:

reducto ad absurdum (naisbodo's spelling): 179 hits

reductio ad absurdam (your spelling): 206 hits

reductio ad absurdum (my spelling): 7140 hits

reductio ad absurdem (a spelling I've seen elsewhere): 117 hits


So, your spelling is more popular than naisbodo's, but considerably less
popular than mine. That doesn't mean you're wrong, but it does mean you
need to defend your accusation with a reference to an independent
authority on the Latin language who supports your view, or withdraw the
accusation altogether.


> is not a rhetorical
> tactic, it is a valid logical method.

Indeed it is. It is also a rhetorical tactic.

<big snip>


>
> > Third and finally, your use of labels does more harm than good. You
> > only communicate your purpose to those who have already taken the time
> > to understand the ideas expressed by your labels, when the ideas they
> > describe are only uncommonly known in the context in which you use
> them.
> > Because of this, you do little good, but this alone does not make your
> > use of them harmful; however, you abuse labels:
> >
> > >>> [...] Fascist [...]
> >
> The label "Fascist" has turned into a sort of verbal stinkbomb

Indeed.

> but note
> that I, in my wordy way, talked of tendencies towards authoritarianism
> which at moments of crisis do become Fascist.
>
> My understanding of Fascism is not based on Spielberg's movies but
> instead on research on "The Authoritarian Personality" performed by
> Theodore Adorno in the 1940s. Adorno's thesis was that in societies in
> economic crisis (such as Weimar Germany) working and middle class
> support for Fascism grows out of people's personal tendencies to
> internalize superego commands AT VARIANCE from their desires.

The problem here is that most people reading this newsgroup (I am
replying in comp.programming) are likely to have formed their
understanding of Fascism either from Spielberg's movies or from
poorly-remembered history lessons. They don't view it in the same
precise way that you do, and (as you pointed out) the word has become
highly emotive rather than descriptive. This can impede understanding.

> I haven't called Steve McConnell a fascist, at all, and he probably
> scores low on Adorno's authoritarianism scale. I've used the word in a
> completely different context, and it is as if the word was not properly
> parsed, but seen as a hot-button or keyword.

This was a predictable outcome. It seems surprising that you did not
predict it.

> This, basically, is not
> my problem, for the seriousness of labor problems in our industry
> (including divorce and suicide) warrants calling a spade a spade.

Quite so. So why do you use such terribly long and unfamiliar words, in
a newsgroup where many of the readership won't understand what *you*
mean by those words, even if they recognise the words themselves?


> You're essentially trying to persuade me to rejoin the problem set, of
> people who phrase false notions in a digestible form.

How about joining the solution set, of people who phrase true notions in
a digestible form?

<snip>


--
Richard Heathfield
"Usenet is a strange place." - Dennis M Ritchie, 29 July 1999.
C FAQ: http://www.eskimo.com/~scs/C-faq/top.html
K&R Answers: http://users.powernet.co.uk/eton/kandr2/index.html

donald tees

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to
spino...@my-deja.com wrote in message <90eu74$v64$1...@nnrp1.deja.com>...

>
>The Foucauldian moment asserts power using pleasure. Therefore, your
>slogan trivializes the very real lack of opportunity for inner city
>people...and also, through oversimplification, characterises all of
>them as pushers, whereas in reality the statistical majority conducts
>itself at a personal level better than upper middle class white people,
>simply because retribution for "lifestyle experimentation" is so brutal
>in the inner city.
>
>This is possibly the major reason why I remain "verbose." 1960s
>politics of slogans and bumper stickers turned liberation into friendly
>fascism.
>>

Harumph.

Using vocabulary designed to impress your audience rather than educating
them does not help. In fact, it further marginalizes your cause. If you
really
want to do something about it, get off your ass, come up here, and I will
give
a programming job in a crack cocaine clinic. This programming office has
put a addict through re-hab every year for the last five. The techniques
are a lot more basic than ranting on about bricolege and Nietzche. You have
to go out on the street and get your hands dirty. Starting a soup kitchen
would be more to the point.

Donald<an old hippie programmer and ex addict>

Tim Bradshaw

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to
"donald tees" <don...@willmack.com> writes:

> Using vocabulary designed to impress your audience rather than
> educating them does not help.

Of course it helps: it helps improve your academic credentials, which
is why people write this stuff.

> In fact, it further marginalizes your cause. If you really want to
> do something about it, get off your ass, come up here, and I will
> give a programming job in a crack cocaine clinic. This programming
> office has put a addict through re-hab every year for the last five.
> The techniques are a lot more basic than ranting on about bricolege
> and Nietzche. You have to go out on the street and get your hands
> dirty. Starting a soup kitchen would be more to the point.

Again, I think you're missing the point. You assume that people who
write this stuff want to help solve real-world problems: they don't,
they want to have academic careers and impress people at dinner
parties.

--tim

Jeff York

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to
spino...@my-deja.com wrote:

>It was cultural. Both Jerry and I had been educated by Catholic
>priests who gave higher grades to longer papers IF there were no errors
>in grammar and spelling. Educated Roman Catholics share with educated
>Arabs, and other cultures supposed more primitive than American free-
>market Protestantism, a love of language whereas in the dominant
>culture time and language are forms of money. ..

I too have a deep love of language. However, once the signal to noise
ratio becomes vanishingly small, content gives way to the sterility of
nothing better than mere mental masturbation..

--
Jeff. Ironbridge, Shrops, U.K.
je...@jakfield.xu-netx.com (remove the x..x round u-net for return address)

... "There are few hours in life more agreeable
than the hour dedicated to the ceremony
known as afternoon tea.."

Henry James, (1843 - 1916).

spino...@my-deja.com

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to
In article <90g6oq$5lg$1...@news.igs.net>,
"donald tees" <don...@willmack.com> wrote:
> spino...@my-deja.com wrote in message <90eu74$v64
$1...@nnrp1.deja.com>...

> >
> >The Foucauldian moment asserts power using pleasure. Therefore, your
> >slogan trivializes the very real lack of opportunity for inner city
> >people...and also, through oversimplification, characterises all of
> >them as pushers, whereas in reality the statistical majority conducts
> >itself at a personal level better than upper middle class white
people,
> >simply because retribution for "lifestyle experimentation" is so
brutal
> >in the inner city.
> >
> >This is possibly the major reason why I remain "verbose." 1960s
> >politics of slogans and bumper stickers turned liberation into
friendly
> >fascism.
> >>
>
> Harumph.

>
> Using vocabulary designed to impress your audience rather than
educating
> them does not help. In fact, it further marginalizes your cause.

If you
> really
> want to do something about it, get off your ass, come up here, and I
will
> give
> a programming job in a crack cocaine clinic. This programming office
has
> put a addict through re-hab every year for the last five. The
techniques
> are a lot more basic than ranting on about bricolege and Nietzche.
You have
> to go out on the street and get your hands dirty. Starting a soup
kitchen
> would be more to the point.
>
> Donald<an old hippie programmer and ex addict>

I've already described how I taught at an inner city trade school. I
also have done volunteer work of the sort you describe, and I myself am
a member of a recovery community.

To me, part of recovery is letting go of personal illusions, and some
of these illusions are formed by culture; it can be considered a form
of deconstruction. For me, one of the illusions of which I let go in
recovery was my fear of being thought pretentious or "verbose" if I let
my light shine. In and out of recovery, I've read a lot of books and
had a lot of street experience, and recovery groups taught me that part
of my problem was trying to be a "real man"...by hiding my knowledge
and speaking in grunts.

I found in the inner city that people actually WANTED to here a shine-
on white boy tell them about Alan Turing, and were confident of their
street ability to filter out his bullshit. Younger people, of all
races, are hungry for any sort of adult male mentoring they can get,
even from an aging shine-on white boy.

For example, I was working out by swimming at the Oak Street Beach last
summer, and some African-American youths asked me to teach them how to
swim. Because of the goddamn neoconservatives and their goddamn war
on "frills" such as midnight basketball and gym class, these kids no
longer had access even to the fucking YMCA, which has been taken over
by the white middle class.

In early recovery I taught a computer training class. I was afraid of
introducing personal insights on the subject matter (the C programming
language) but the president of the training firm, a personal friend who
knew my recovery history, told me that while some of what I wanted to
say was BS other consisted of valuable personal experience in
programming that would make the class more interesting.

It is true that many addicts hide their fear and addiction behind a sea
of words. But other addicts (especially men) fail to verbalize ENOUGH.

Marco S Hyman

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to
spino...@my-deja.com writes:

> > > ALSO find good ideas in B school work. If few add to or transmit from
> > > human knowledge *per se*, their value nonetheless resides in the way
> > > they enhance people's lives, by, for example, showing them how to
> > > program in Visual Basic, and thereby earn a living without selling
> > > drugs. Some of the work done at the private, for-profit University of
> >
> > Visual Basic: it keeps pushers off the streets!
>
> Note the Foucauldian moment we are enjoying here. I learned Visual

Nope. I just applied a little Strunk and White to your statement.
Perhaps it's time for you to review "The Elements of Style" again.
May I suggest sections "V.6 Do not overwrite" and "V.7 Do not overstate".

// marc

Peter Seebach

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to
In article <90ehr2$m12$1...@nnrp1.deja.com>, <spino...@my-deja.com> wrote:
>Now, this in itself does not indicate that I am not verbose.

I stopped reading at this point, because I lost track of why I had started
reading.

-s
--
Copyright 2000, All rights reserved. Peter Seebach / se...@plethora.net
C/Unix wizard, Pro-commerce radical, Spam fighter. Boycott Spamazon!
Consulting & Computers: http://www.plethora.net/

Peter Seebach

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to
In article <3A2B6F01...@antlimited.com>,

Richard Heathfield <ric...@antlimited.com> wrote:
>Since you're talking about software engineering, I might as well point
>out that the IOCCC is a marvellous example of how *simple* thoughts can
>be expressed in a *complex* way.

And we're nearly done! Really! I mean it! In about half an hour we'll
be discussing the final winners. :)

Peter Seebach

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to
In article <90feg0$b23$1...@nnrp1.deja.com>, <spino...@my-deja.com> wrote:
>In article <3a2b1379...@news.shuswap.net>,
> ge...@shuswap.net wrote:
>> Interesting. I've found that people who retreat behind dense
>> jargon-laden polysyllablism are often trying to hide that they don't
>> know what they are talking about. Sometimes, they hide their
>> ignorance from themselves, but are usually less successful in fooling
>> others.

>Gee, my experience in programming is quite the opposite.

Really?

>If you can
>say "This module does this", accurately, using as many words as it
>takes, you know more than the inarticulate bozo who just codes.

Certainly.

But if, instead, you go on for three pages using big words that aren't
necessary, you probably know less than the guy who actually wrote *only*
as many words as it takes, rather than a great deal of extra wording.

Marco S Hyman

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to
spino...@my-deja.com writes:

> So you can take your Strunk and White and shove it up your ass (and how
> is that for simple, manly, Anglo-Saxon style?) Lanham points out that

Short, simple, and to-the-point. Too bad you didn't start your
little essay with this comment. It would have placed the remainder
of your thoughts in their proper context.

// marc

Al Dunbar

unread,
Dec 4, 2000, 3:00:00 AM12/4/00
to

<spino...@my-deja.com> wrote in message
news:90hkqa$4l7$1...@nnrp1.deja.com...

> In article <3A2B6F01...@antlimited.com>,
> Richard Heathfield <ric...@antlimited.com> wrote:
> > spino...@my-deja.com wrote:
> > >
> > > In article <90f597$o4a$1...@bob.news.rcn.net>,
> > > naisbodo <nais...@enteract.com> wrote:>

<snip - and bookmark the following line:>

> It is arrogant because you define the audience. Nothing gives you that
> right.

<now read the following:>

> Bite me. I know a little Latin, and if you think for one fucking
> minute I am going to take the votes of thousands of mental defectives
> you've got another thing coming.

What gives *you* the right? At least Richard's definition of the audience
was polite.

/Al


spino...@my-deja.com

unread,
Dec 4, 2000, 8:42:57 PM12/4/00
to
In article <nkjk89g...@tfeb.org>,
Tim Bradshaw <t...@tfeb.org> wrote:

> "donald tees" <don...@willmack.com> writes:
>
> > Using vocabulary designed to impress your audience rather than
> > educating them does not help.
>
> Of course it helps: it helps improve your academic credentials, which
> is why people write this stuff.

The folk notion that contemporary academics write in order to advance
their careers is wrong.

First of all, publish or perish is only true at first-tier
institutions. Less prestigious private colleges and many state schools
have written policies that place teaching first, and opportunities for
any kind of research are treated as perks and rewards for loyalty. Use
of these opportunities at these schools is not so much career advancing
as a SIGN of favor.

For example, the chair of the department of philosophy where I went to
school published several books while at my school and subsequently at a
state school. He was nominated at the end of his career for a state
award but did not receive it because, he was told, he had written TOO
MUCH. This is publish and perish, for to write several books attracted
the resentment of the faculty who found it difficult to maintain this
man's productivity while at the same time having his heavy teaching
load.

Second and most important, it might occur to you that hard-working,
underpaid academics resent the very idea that by doing a significant
part of their jobs as typically understood, participating in the
production of knowledge, they are thereby being pretentious little
twits. Perhaps you would like a society in which the only intellectual
work performed was immediately paid for, and changed to private
property.

>
> > In fact, it further marginalizes your cause. If you really want to
> > do something about it, get off your ass, come up here, and I will
> > give a programming job in a crack cocaine clinic. This programming
> > office has put a addict through re-hab every year for the last five.
> > The techniques are a lot more basic than ranting on about bricolege
> > and Nietzche. You have to go out on the street and get your hands
> > dirty. Starting a soup kitchen would be more to the point.
>

> Again, I think you're missing the point. You assume that people who
> write this stuff want to help solve real-world problems: they don't,
> they want to have academic careers and impress people at dinner
> parties.
>
> --tim

Another urban legend and folk myth is that there is out there a sort of
Georgtown or Cambridge "set" of liberal elitists who have dinner and/or
cocktail parties, drinking Pink Ladies and partaking of other tutti-
frutti delights. In actual fact and in my direct experience, including
five years at Princeton University, there's not so much "impressing
people at dinner parties" as there is hard work in academia.

An academic careerist is a fool simply because of the low demand for
most scholars in most fields. Today, he or she has to have some
dedication to the very idea that learning for its own sake is valuable
and rewarding. This of course attracts the resentment of the sullen
corporate types who long ago cut off their nuts for a paycheck, whence
these folk tales.

spino...@my-deja.com

unread,
Dec 4, 2000, 9:00:58 PM12/4/00
to
In article <x7bsust...@hana.snafu.org>,

Marco S Hyman <ma...@snafu.org> wrote:

I've of course read Strunk and White, that totem, long ago: but I have
also read Richard Lanham's 1974 comments on Strunk and White which
place this manual in historical context.

Strunk and White were writing about the needs of private magazines (in
their case the New Yorker of Harold Ross) in which the real financial
cheesecake is not the articles but the ads. Essentially, their mission
at the time (which was rather long ago) was to eliminate the long
articles that actual readers demanded in the 19th century, in favor of
snappier content that people in the 1920s and 1930s demanded.

Their financial mission, as far as Harold Ross was concerned in the
Depression, was to ensure that the magazine stayed afloat. This
required some "labor discipline" on the part of the authors, and
editing out their favorite parts, while sometimes necessary, also
conveniently sent the message that they did not own the printing press.

The trend of actual demand DID move towards simpler content over the
period 1930..2000: however, by the 1980s, it became moronizing, as in
USA Today, where the simplicity of the style destroys content
altogether. At the New Yorker, Tina Brown continued the simplifying
and moronizing trend until the magazine was abandoned by its natural
constituency who although time-challenged still wanted a reasonable
level of complexity in the articles and after Brown got her cute little
butt booted out of the New Yorker, its articles have once again gotten
longer and more interesting.

Strunk and White is out of date in a multicultural world, as Lanham
pointed out some time ago. Thus I am offended by their favoring of
Anglo Saxon words as against words of Norman-French derivation: for
this discounts my high school Latin and somewhat discriminates against
my Catholic culture. I can well imagine that they give higher offense
to Latino and black students who would write well were it not for the
minatory use of an outdated guide.

So you can take your Strunk and White and shove it up your ass (and how
is that for simple, manly, Anglo-Saxon style?) Lanham points out that

the best way to learn to write is to read, and the real problem in
teaching writing (as I have) is that students don't read. I'd add that
my academic experience is that by today, TEACHERS don't read (Saul
Bellow asked a fellow faculty member at the University of Chicago how
he liked the new library: the teacher replied that he wouldn't know
since he did not read outside journals in his field.) As a result,
students in writing classes are frequently abused with Strunk and White
by teachers who hate the written word, and would be rather watching TV
themselves.
>
> // marc

spino...@my-deja.com

unread,
Dec 4, 2000, 9:20:24 PM12/4/00
to
In article <t2mj8n...@corp.supernews.com>,

You just don't get the reality of power in our business, do you, Al?
No, I didn't want to get the reputation within my company as being
critical of software engineering since along with my wife I was
responsible for their support.

Many programmers who questioned software engineering are driving cabs
because they were forced out of the business.

Now that my kids are grown, I feel freer to express these views. I've
also found that being a yes-man and an empty suit doesn't really work
either. Finally, in the present economy (which may of course bust at
any time) my skills are in such demand I can say what I feel.

Your resentment of my manner of expression is part of the problem, Al,
and in my original review I did mention how the anti-intellectualism of
the average programmer is used to ensure that management is always in
control. It's actually Bertolt Brecht's "culture is dogshit" mistake
(if we can consider programming a form of culture.) Brecht rejected
high culture because it was alien to the worker, who wanted football
and beer. Brecht failed to see how football and beer were themselves
commodities and could themselves control the worker.

The real revolutionary wears a suit and tie, like Malcolm X, and, like
Malcolm, calls on his followers to act with the same dignity as the
ruling elite. My claim is that the high-tone talk of "science" in
software engineering needs to be met, not with inchoate muttering and
drooling, but with even higher-toned analysis of its cultural and
scientific origins.

Here's an example. Suppose you are asked to write a report by your
manager and the manager tells you it is too long, and quotes Polonius'
speech in Hamlet, where Polonius admonishes Laertes not to use too many
words. It is a common management technique in engineering, for the
manager to show that he has more humanities cultural depth: women
managers are especially fond of this.

But if you actually read Shakespeare (or rent Ken Branagh's excellent
movies) you can come right back with the fact that we need not take
Polunius' advice, for it's obvious Shakespeare thought Polonius was a
damnfool, and Polonius, in a later scene with Gertrude, himself is
overly prolix. Shakespeare, who used far more words than the average
playwright of his time, had no brief for terseness for its own sake.

The very fact, that I pointed out in the first paragraph of my review,
that for years these "programmers BAD: software engineering GOOD" tomes
have been written without any real change, shows that programmers with
disquiet about this power/knowledge need to be something more than
unreconstructed, aging hippies about it. Their very culture keeps them
where they are. It is informed by an unexamined 1960s cynicism about
culture and a skepticism about the possibility of knowledge that is all
too ready to say that software engineering is dogshit...but plays along
nonetheless, reproducing the real dogshit year after year.

>
> /Al

spino...@my-deja.com

unread,
Dec 4, 2000, 9:44:27 PM12/4/00
to
In article <3A2B6F01...@antlimited.com>,
Richard Heathfield <ric...@antlimited.com> wrote:
> spino...@my-deja.com wrote:
> >
> > In article <90f597$o4a$1...@bob.news.rcn.net>,
> > naisbodo <nais...@enteract.com> wrote:>
> > Ironically, we all accept this as regards science and
> > mathematics
>
> Simple examples of complex thought which can be expressed simply:
>
> F = ma (from Newtonian mechanics)
> E = mcc (from relativity theory - sorry for the absence of
> subscripts...)

This is a nonsensical example, for anyone who knows only that f=ma or
even the words "force equals mass times acceleration" or "energy equals
the speed of light squared times mass" knows neither general relativity
nor Newtonian mechanics AT ALL.

This is like the manager who writes down phrases in a meeting and
passes them along as knowledge to programmers, without finding what the
phrases mean.


> >
> > Shakespeare's plays often express complex thoughts about personality
> > and human relationships, and his vocabulary was large and likewise
his
> > sentence structure.
>
> Sure. So?

So gee Shakespeare should knew how to write, huh?


>
> >
> > Your "simplicity" is a psychological, reader-response predicate
which
> > is an attribute of the reader's reception.
>
> How do you know that? Perhaps his simplicity is just simple.
>
> Defining simplicity is actually an alarmingly complex activity!
>

Yes.


> <snip>
>
> > For if you reduce the word count by allowing what you call big words
> > and what I call terms of art, the writer is under the charge of
using
> > big words and terms of art. If you prohibit the big words, the
writer
> > is charged with verbosity. His thoughts (including his desire for
> > charity and nuance) are at times conveniently silenced.
>
> There's a place to use big words, and that place is in a forum and
> context where everyone likely to read or hear those words is likely to
> garner your intended meaning, and where communication is more
effective
> because of the bigness of the words.
>

I do not so much use big words as sentence structure, in a forum where
the majority of writers prefer telescoped sentence structure. The
humorist Dave Barry noticed long ago that the Internet is a guy
phenomenon, and guys think it prissy to use complex sentence
structures. They prefer the directness of Indian Companion in the
prologue to South Park:

"Someone coming." - Indian Companion

But the real arrogance is not to use either big words or sentence
structure: it is instead to say, as so many guys in this thread have
said in different ways, "Ho, me Normal Person and me no like your big
words and forked tongue, for it is better to be simple and to eat bread
and salt and speak truth."

[I do not want to give offense here to Native Americans, so I switched
to a Russian proverb. I'll also point out that Native Americans are
caricatured by the "silent Indian" image and there is a wealth of
stories and songs from Native Americans. I am talking about the
cultural baggage of Internet honchos.]

It is arrogant because you define the audience. Nothing gives you that
right.

> There's a place to use little words, and that place is in a forum and


> context where the bigger words would confuse a significant proportion
of
> your audience or readership. In this case, the forum is
> comp.programming, a technical discussion newsgroup (always re-read
> before posting! - I note that this is cross-posted to two newsgroups
> with which I am unfamiliar, alt.folklore.computers and comp.software-
eng
> - so I don't know whether my point is valid in those newsgroups), but
> the context has little or nothing to do with the technical side of
> programming. Therefore, leaving topicality issues aside for the
moment,
> little words are appropriate. Those big words which don't enjoy wide
> understanding within the programming community which this newsgroup
(or
> these newsgroups!) represents should either be defined as you go or
> eschewed (rejected) altogether.
>

Actually, I was trying to get to comp.programming but it appears I have
been waylaid by an eternal discussion of writing style. The real
violation of the charter of comp.programming was to raise the issue of
my writing style in the first place.

However, writing style does have a lot to do with programming: this was
first noticed in the 1970s by Brian Kernighan. Basically, programming
tends to press some of the same cultural buttons, and to cause the same
resentments, as does writing. Many programmers actually hate "clean",
elegant code because it is a cultural reproof to their self-perceived
lack of ability, and their unspoken anxieties about whether they really
belong in the programming racket at all.

>
> Not really. It's possible to call a spade a manually operated
> agricultural excavation implement, and it's possible to summarise the
> complex behaviour of a body in a gravitational field with a simple
> equation. Therefore, examples exist which show that it is possible for
> complexity of expression to be unrelated to complexity of thought, and
> therefore they are separate measures. Therefore, he is correct.
>

But you CANNOT meaningfully say you are not wasting the audience's time
when you merely precis the complex behavior by stating the final
formula. You have to bring the audience up to speed. Likewise, when
I've talkked about cultural theory, I have at least tried to explain
whatinhell Foucault was talking about, whence the "verbosity."

> >
> > For in no final sense can we speak of "measuring complexity"
although
> > software engineers talk as if this is a given. Thought precedes
> > numeration and therefore to measure complexity is deep nonsense.
>
> To measure complexity objectively is difficult, if not impossible. To
> measure it heuristically and subjectively is something most people
> reading this newsgroup will do on most days. Hardly nonsense.
>

They think they are measuring because they are geeks who think that
measuring, as opposed to logical analysis, is the first act of
cognition. In reality, they are having an emotional meltdown because I
make it plain that cultural forces are arrayed against them.

> >
> > This was seen in the early days of software engineering when lines
of
> > code were used as a metric.
>
> It was not foolish to seek to measure software complexity. It is
foolish
> to use lines of code as your sole metric. We "know" intuitively that a
> 10,000,000 line program is more complex than a 10 line program. What
we
> can't know is that a 2,000 line program is more complex than a 1,000
> line program.
>

You should check out some of the one-liners in the Obfuscated C
Contest. There are examples that are far more complex than a program
like:

i = i + 1 {repeated 10,000,000 times)

Size of code is an IRREVELANT measure.

Bite me. I know a little Latin, and if you think for one fucking


minute I am going to take the votes of thousands of mental defectives

you've got another thing coming. "um" is NOT the correct ending.

>
> > is not a rhetorical
> > tactic, it is a valid logical method.
>
> Indeed it is. It is also a rhetorical tactic.
>

Only in the trivial sense that we use logic when we use rhetoric. The
ordinary meaning of rhetoric refers to nonlogical moves such as appeal
to emotions. Reductio does nothing of the sort.

This shows little enough respect for ability to learn.

Natarajan Krishnaswami

unread,
Dec 4, 2000, 10:20:34 PM12/4/00
to
On Tue, 05 Dec 2000 02:44:27 GMT, spino...@my-deja.com <spino...@my-deja.com> wrote:
> Bite me. I know a little Latin, and if you think for one fucking
> minute I am going to take the votes of thousands of mental defectives
> you've got another thing coming. "um" is NOT the correct ending.

Sorry, -um really is the correct ending: 'absurdam' is the accusative
(object of 'ad') of (feminine) 'absurda', whereas the phrase needs the
accusative form of (neuter) 'absurdum', which is 'absurdum'.

If you're going to be a pedant, at least be right.


<N/>

naisbodo

unread,
Dec 4, 2000, 11:07:49 PM12/4/00
to
In comp.programming Natarajan Krishnaswami <nx...@po.cwru.edu> wrote:
> On Tue, 05 Dec 2000 02:44:27 GMT, spino...@my-deja.com <spino...@my-deja.com> wrote:
>> Bite me. I know a little Latin, and if you think for one fucking
>> minute I am going to take the votes of thousands of mental defectives
>> you've got another thing coming. "um" is NOT the correct ending.
>
> Sorry, -um really is the correct ending: 'absurdam' is the accusative
> (object of 'ad') of (feminine) 'absurda', whereas the phrase needs the
> accusative form of (neuter) 'absurdum', which is 'absurdum'.

Yah. Sorry I ever brought the phrase up in the first place--I haven't
studied Latin that much, it was only something I learned when I studied
logic. I didn't realize this was going to turn into a spelling-flame-
pissing match intended to prove that Spinoza's superiority compared to
the rest of the world.

But then, that's all this thread was from the beginning, sans spelling
flame, and I apologize for having drawn out the initial discussion in
vain. Apologies also to alt.folklore.computers and comp.software-eng,
which undoubtedly have been as irritated by this thread as the group in
which I am reading it.

(My previous message would have been my last, but I felt I owed the
above groups an apology for contributing to the length of this thread.)

--
nais...@enteract.com
http://www.naisbodo.com/

Jay Maynard

unread,
Dec 4, 2000, 11:27:01 PM12/4/00
to
On 5 Dec 2000 04:07:49 GMT, naisbodo <nais...@enteract.com> wrote:
>Apologies also to alt.folklore.computers and comp.software-eng,
>which undoubtedly have been as irritated by this thread as the group in
>which I am reading it.

I've been wondering just what the precise hell this whole subject has been
doing in afc, where I read it...but then, given spinoza9999's overwhelming
sense of moral and intellectual superiority, I'm sure he'll argue that he's
got the right - nay, the duty - to let us all know about his crusade,
whether we're interested in hearing about it or not.

spino...@my-deja.com

unread,
Dec 5, 2000, 12:11:53 AM12/5/00
to
In article <x7wvdfs...@hana.snafu.org>,

Marco S Hyman <ma...@snafu.org> wrote:
> spino...@my-deja.com writes:
>
> > So you can take your Strunk and White and shove it up your ass (and
how
> > is that for simple, manly, Anglo-Saxon style?) Lanham points out
that
>
> Short, simple, and to-the-point. Too bad you didn't start your
> little essay with this comment. It would have placed the remainder
> of your thoughts in their proper context.

Indeed, but note that thereby I become a sound byte and a cartoon
troll. I ain't no fucking sound byte and I ain't no cartoon troll.

Note how in Steve's book he marginalizes the opposition to
certification, by quoting the bandidos in John Huston's film The
Treasure of the Sierra Madre:

Badges? We don' need no badges. We don' need no stinking badges!

Steve does so in a fashion that is both racist and colonialist, for
Huston's film portrayed Mexico as a land of bandidos, and Federales
scarcely distinguishable from bandidos. Since this autumn, Mexico has
managed to elect a Presidente and we have not, it is understandable
that Mexicans might resent caricature.

It is also likely that educated people with degrees, who have not
passed certification tests, might resent being internally colonized and
lumped with thieves as well.

spino...@my-deja.com

unread,
Dec 5, 2000, 12:29:30 AM12/5/00
to
In article <t2mk6e2...@corp.supernews.com>,

"Al Dunbar" <Al_D...@HoTMaiL.com> wrote:>
> > I'd suggest, Al, that reading some of the texts might help your
case,
> > and that part of my verbosity is simply a density of references.
>
> Exactly. It is as if you cannot speak directly on your own, but need
to
> constantly make references to various philosophers and others in the
> mistaken belief that this will impress the fight out of the
opposition.

Al, referring to previous work is simple common courtesy to the author,
and I went into this knowing full well that programmers of my
generation and younger are singularly unimpressed by references to
works they do not think they have time to read. Note that the goal is
a sort of war of the buffoons, in which subordinated intellectuals of
the dominant class enforce their internal pecking order by attacking
praxis (referring to previous work) which is expected in published
work.

One is instead to engage in content-free rumination, New Age horseshit,
and flaming easy targets (such as H1-Bs, as in alt-computer-
consultants.) That keeps things safely virtual.

Solipsistic talk inspired by recovery groups is encouraged in which the
poster presents himself as a misunderstood and lonely cuddly-bear with
feelings that cannot be gainsaid. Or, equally solipsistic talk,
informed by hatred, is welcome because again even negative feelings
cannot be gainsaid...in a society in which people insist that prisoners
be executed because it is part of their "recovery process."

What appears to be pretentious and completely out of the question, like
farting in church, is the claim of knowledge. References are checkable
and thus a false reference would be a stupid move. Nonetheless, in an
Internet dominated by the feelings of overworked garden gnomes who do
not have time to read anything outside their field, references are
nothing more than pretense.

You haven't bothered, I note, to check up on Gilb, or for that matter
even read Steve McConnell's book. Instead you restrict yourself to a
critique of writing style when I have made it clear that the medium is
the message. You've also encouraged less principled posters to flame
away (based on the little boy's law, that any uniqueness is to be
badgered by the mob) thus trivializing what remains an important
issue.

spino...@my-deja.com

unread,
Dec 5, 2000, 12:32:55 AM12/5/00
to
In article <t2mh2ga...@corp.supernews.com>,

"Al Dunbar" <Al_D...@HoTMaiL.com> wrote:
>
> <spino...@my-deja.com> wrote in message
> news:90eu74$v64$1...@nnrp1.deja.com...
> > In article <x7d7f93...@hana.snafu.org>,

> > Marco S Hyman <ma...@snafu.org> wrote:
> > > spino...@my-deja.com writes:
> > >
>
> <snip>

>
> > This is possibly the major reason why I remain "verbose."
>
> I thought you remained verbose in order to disprove our assertion
that you
> were verbose, a statement that you took exception to some posts ago.

For probably the last time, let me spell it out for you in simple terms.

You haven't read the book in question (apparently.)

Therefore you were *prima facie* unqualified to start a discussion.

Nonetheless you jumped in with a (layperson's) critique of writing
style, wasted my time, and ignited a flame war as other posters saw
their chance to join a small herd, teasing and otherwise badgering a
poster whose style differed from the half-literate norm.

Shame on you.
>
> /Al
>
> > > // marc

Steve Merrick

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
What's the war about? Someone contributed a review of a book. Whether
you liked the review or not, it couldn't *decrease* what you know of the
book, so how could it harm you? If you didn't like the review, why not
just ignore it? All I can see is a group of people feeling threatened,
and blustering accordingly. It's time to back away from this silliness
before it turns into a fight.

I enjoyed the review. Thank you.

--
Steve Merrick

Richard Heathfield

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
[My last article in this thread]

spino...@my-deja.com wrote:
>
> In article <3A2B6F01...@antlimited.com>,
> Richard Heathfield <ric...@antlimited.com> wrote:
> > spino...@my-deja.com wrote:
> > >
> > > In article <90f597$o4a$1...@bob.news.rcn.net>,
> > > naisbodo <nais...@enteract.com> wrote:>
> > > Ironically, we all accept this as regards science and
> > > mathematics
> >
> > Simple examples of complex thought which can be expressed simply:
> >
> > F = ma (from Newtonian mechanics)
> > E = mcc (from relativity theory - sorry for the absence of
> > subscripts...)
>
> This is a nonsensical example,

No, it isn't.

> for anyone who knows only that f=ma or
> even the words "force equals mass times acceleration" or "energy equals
> the speed of light squared times mass" knows neither general relativity
> nor Newtonian mechanics AT ALL.

Very true, but the example is not nonsensical because it demonstrates
how complex ideas can be expressed simply, which was the point. I did
not and do not claim that these expressions suffice for a full
understanding of the entire subjects in which they are relevant.

Read for comprehension, sir.

>
> This is like the manager who writes down phrases in a meeting and
> passes them along as knowledge to programmers, without finding what the
> phrases mean.

No, it's more like programmers being able to communicate complex ideas
in conversations like:

"What's the best way to store these IPs? Tree or hash?"
"Use a hash - quicker, less RAM".

Complex ideas, simple expression.

Read for comprehension, sir.


>
> > >
> > > Shakespeare's plays often express complex thoughts about personality
> > > and human relationships, and his vocabulary was large and likewise
> his
> > > sentence structure.
> >
> > Sure. So?
>
> So gee Shakespeare should knew how to write, huh?

^^^^

Mr Spelling-Bee, huh?

Citing one example of a playwright who expresses some complex ideas in
complex ways does not prove that all complex ideas must be expressed in
complex ways.

Read for comprehension, sir.


<snip>


> >
> > There's a place to use big words, and that place is in a forum and
> > context where everyone likely to read or hear those words is likely to
> > garner your intended meaning, and where communication is more
> effective
> > because of the bigness of the words.
> >
> I do not so much use big words as sentence structure, in a forum where
> the majority of writers prefer telescoped sentence structure.

This is indeed true (although some people might reasonably claim that
you /also/ use big words), but it is irrelevant.

> The
> humorist Dave Barry noticed long ago that the Internet is a guy
> phenomenon, and guys think it prissy to use complex sentence
> structures.

I am perfectly prepared to read, and indeed to use, complex sentence
structures, when I consider them to be necessary and appropriate to the
point I am making, and likely to be comprehensible to my intended
readership. If I am writing for a readership which is not experienced in
the use of technical jargon, I either won't use any or will define the
terms I use as I use them. When one is addressing technical newsgroups
such as the ones to which you posted your article, one cannot sensibly
assume that one's intended readership is fully conversant with the
meanings of words like "epistemological". Thus, if one needs to use such
a word, one ought to define it.

I fail to see the relevance of Dave Barry, or his observation, to this
discussion, since the generalisation he makes, like all generalisations
(including this one), is false.

<snip>



> But the real arrogance is not to use either big words or sentence
> structure: it is instead to say, as so many guys in this thread have
> said in different ways, "Ho, me Normal Person and me no like your big
> words and forked tongue, for it is better to be simple and to eat bread
> and salt and speak truth."

It depends on your intention. If you're seeking to impress, use big
words and damn the consequences (such as this overly-long thread). If
you're seeking to inform, consider your audience.

It strikes me that you're far more interested in impressing people than
with informing them, and that you have failed on both counts.

>
> [I do not want to give offense here to Native Americans,

You gave it your best shot, though, didn't you?

> so I switched
> to a Russian proverb.

Going for the double-whammy?

> I'll also point out that Native Americans are
> caricatured by the "silent Indian" image and there is a wealth of
> stories and songs from Native Americans.

What on Earth has this to do with what we're discussing?

> I am talking about the
> cultural baggage of Internet honchos.]

a) this is Usenet, not the Internet. Usenet can use the Internet, but
does not have to.
b) You appear to be making the mistake that many Usenetters do, of
assuming that everyone in the world is an American, with American
cultural norms, values, and referents. For example, I'm not entirely
clear what you mean by a "honcho".


> It is arrogant because you define the audience. Nothing gives you that
> right.

I don't define the audience of comp.software-eng, comp.programming, or
alt.folklore.computers. The topic defines the audience in each of those
newsgroups.


> Actually, I was trying to get to comp.programming but it appears I have
> been waylaid by an eternal discussion of writing style. The real
> violation of the charter of comp.programming was to raise the issue of
> my writing style in the first place.

Write for comprehension, sir. Very few people had a clue what you were
talking about. I've just re-read your original article, and I have to
say I found it a hilarious exercise. Did you really think that the
majority of your selected readership would be able to understand, or
care about, most of what you wrote?


> However, writing style does have a lot to do with programming: this was
> first noticed in the 1970s by Brian Kernighan. Basically, programming
> tends to press some of the same cultural buttons,

I have no idea what you mean by "cultural button". I'm picturing a large
coat-button visiting an art gallery, which obviously isn't what you
meant.

> and to cause the same
> resentments, as does writing. Many programmers actually hate "clean",
> elegant code

I don't know of a single programmer who hates clean, elegant code. You
obviously mix in different circles to me.

> because it is a cultural reproof to their self-perceived
> lack of ability,

I also don't know any programmers with a self-perceived lack of ability.
The opposite problem is more usually the case.

> and their unspoken anxieties about whether they really
> belong in the programming racket at all.

If they are unspoken, how can you know that these anxieties exist?


> > It's possible to call a spade a manually operated
> > agricultural excavation implement, and it's possible to summarise the
> > complex behaviour of a body in a gravitational field with a simple
> > equation. Therefore, examples exist which show that it is possible for
> > complexity of expression to be unrelated to complexity of thought, and
> > therefore they are separate measures. Therefore, he is correct.
> >
>
> But you CANNOT meaningfully say you are not wasting the audience's time
> when you merely precis the complex behavior by stating the final
> formula.

My dear chap, the proposition was that complex ideas cannot be expressed
simply, and I have defeated it. I have not said that all complex ideas
can be expressed simply, and I have not said that an entire scientific
discipline or even sub-discipline can be summed up in one equation. I
have merely pointed out that equations are a good way to express complex
ideas simply, thus defeating your proposition.

Read for comprehension, sir.

> You have to bring the audience up to speed.

Sometimes you do, and sometimes you don't. When I suggest to a fellow
programmer that he might consider using a deque as an appropriate
solution to his problem, I can confidently expect that he will know what
I mean, and if he's unfortunate enough not to have met the term, he can
ask for clarification, which can be given in a few words - "it's a
double-ended queue - you can add and remove from either end". I don't
have to spend huge amounts of time explaining the concept, because he
already has a good understanding of the field.

When you are trying to explain something foreign to your selected
readership's experience, however, you do need to spend a lot more time
bringing them up to speed.

> Likewise, when
> I've talkked about cultural theory, I have at least tried to explain
> whatinhell Foucault was talking about, whence the "verbosity."

Just out of sheer curiosity, what led you to believe that your article
would be of interest to the newsgroups you selected?

>
> > >
> > > For in no final sense can we speak of "measuring complexity"
> although
> > > software engineers talk as if this is a given. Thought precedes
> > > numeration and therefore to measure complexity is deep nonsense.
> >
> > To measure complexity objectively is difficult, if not impossible. To
> > measure it heuristically and subjectively is something most people
> > reading this newsgroup will do on most days. Hardly nonsense.
> >
> They think they are measuring because they are geeks

Ah, you'll have to define "geek", I'm afraid.

> who think that
> measuring, as opposed to logical analysis, is the first act of
> cognition.

I know of nobody else who thinks this. I'm beginning to wonder whether
we are from the same planet.

> In reality, they are having an emotional meltdown because I
> make it plain that cultural forces are arrayed against them.

No, they're having great fun flaming you because you're arrogant,
pretentious, wordy, and a poor judge of your readership.


> > > This was seen in the early days of software engineering when lines
> of
> > > code were used as a metric.
> >
> > It was not foolish to seek to measure software complexity. It is
> foolish
> > to use lines of code as your sole metric. We "know" intuitively that a
> > 10,000,000 line program is more complex than a 10 line program. What
> we
> > can't know is that a 2,000 line program is more complex than a 1,000
> > line program.
> >
> You should check out some of the one-liners in the Obfuscated C
> Contest. There are examples that are far more complex than a program
> like:
>
> i = i + 1 {repeated 10,000,000 times)

So, like I said, we "know" intuitively that a 10 MLOC program is more
complex than a 10 line program, but we cannot know that a 2 KLOC program
is more complex than a 1 KLOC program. The second half of the sentence
indicates that counter-examples can exist; you have pointed out another
counter-example - big deal. Nevertheless, in general terms, big programs
tend to be more complicated than little programs.

>
> Size of code is an IRREVELANT measure.

No, it's not. It's a heuristic, and a useful one. That's not to say that
it's solid enough to base, say, remuneration on (and, indeed, if you
did, you'd end up with your program where i++ is repeated 10,000,000
times, human nature being what it is), but it's one indicator of
complexity. It can't be used alone, and it may not even be a major
indicator, but it is certainly one of the things one takes into account
when looking at code complexity.

>
> > > "Measuring complexity" is reification for it makes a thing out of a
> > > concept which exists primarily in a network of concepts. It also
> > > allows the measurer's personal bias to be presented as Science.
> >
> > Measuring complexity is something we do every day. The fact that we
> > can't measure it with a ruler or a balance is neither here nor there -
> > we make heuristic judgements of complexity regularly. Sometimes,
> > therefore, we make wrong judgements. But we get it right often enough
> > that we consider it worth continuing to do.

I've left this bit in, even though you didn't reply to it, because I
think you should have replied to it It is a direct rebuttal of what you
said, so I'd be interested to hear your reaction to it.

> > > > Second, you're using the rhetorical tactic of reducto ad absurdum
> in
> > > > your examples:
> > >
> > > "Reductio ad absurdam" (the correct spelling)
> >

<snip Websearch stats>

> >
> > So, your spelling is more popular than naisbodo's, but considerably
> less
> > popular than mine. That doesn't mean you're wrong, but it does mean
> you
> > need to defend your accusation with a reference to an independent
> > authority on the Latin language who supports your view, or withdraw
> the
> > accusation altogether.
>
> Bite me. I know a little Latin

So do I. If you're going to correct people's spelling, get the spelling
right yourself.

At present, your assertion that you are correct is just that - an
assertion. It has no more validity than mine. If you want to pick holes
in people's spelling, a most unUsenettish thing to do (except in revenge
for having it done), you'd better be able to prove that your correction
is correct, and proof requires more than assertion.

Indeed, it was your incorrect correction of naisbodo's spelling which
prompted me to send my original reply.


>, and if you think for one fucking
> minute I am going to take the votes of thousands of mental defectives

Ah, how revealing. This is how you talk, and how you view your fellow
Netizens, when you've forgotten you're supposed to be intellectual, is
it?

> you've got another thing coming.

ITYM "think". If you criticise other people's spelling, be damn sure
your own is correct.

> "um" is NOT the correct ending.

Your assertion is meaningless without independent and authoritative
evidence.

> > > is not a rhetorical
> > > tactic, it is a valid logical method.
> >
> > Indeed it is. It is also a rhetorical tactic.
> >
> Only in the trivial sense that we use logic when we use rhetoric. The
> ordinary meaning of rhetoric refers to nonlogical moves such as appeal
> to emotions. Reductio does nothing of the sort.

If reductio ad absurdum were not a rhetorical tactic, it could not be
used rhetorically.

I am using it rhetorically.

Therefore, it is a rhetorical tactic.

[The Fascism bit]

> >
> > The problem here is that most people reading this newsgroup (I am
> > replying in comp.programming) are likely to have formed their
> > understanding of Fascism either from Spielberg's movies or from
> > poorly-remembered history lessons. They don't view it in the same
> > precise way that you do, and (as you pointed out) the word has become
> > highly emotive rather than descriptive. This can impede understanding.
> >
> This shows little enough respect for ability to learn.

I'd have thought it showed a healthy respect for people's ability to
select newsgroups and academic subjects in which they are interested.
Fascism (in the strictly accurate sense of that word) is not a topic
which one goes looking for in programming newsgroups; those in your
audience who don't know what Fascism really is (and I'll bet it's most
of them) /don't care/ what Fascism really is; otherwise, they'd have
gone and found out. Those few who do care either will go and find out
now, or have already found out and therefore already know.

Read for comprehension, sir. Read for comprehension.

Jeff York

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
spino...@my-deja.com wrote:

>In article <3A2B6F01...@antlimited.com>,
> Richard Heathfield <ric...@antlimited.com> wrote:
>> spino...@my-deja.com wrote:
>> >

>> > "Reductio ad absurdam" (the correct spelling)
>>
>> The Web is not known for its devotion to accuracy. Nevertheless, here
>> are some Web search findings:
>>
>> reducto ad absurdum (naisbodo's spelling): 179 hits
>>
>> reductio ad absurdam (your spelling): 206 hits
>>
>> reductio ad absurdum (my spelling): 7140 hits
>>
>> reductio ad absurdem (a spelling I've seen elsewhere): 117 hits
>>
>> So, your spelling is more popular than naisbodo's, but considerably
>less
>> popular than mine. That doesn't mean you're wrong, but it does mean
>you
>> need to defend your accusation with a reference to an independent
>> authority on the Latin language who supports your view, or withdraw
>the
>> accusation altogether.
>
>Bite me. I know a little Latin, and if you think for one fucking
>minute I am going to take the votes of thousands of mental defectives
>you've got another thing coming. "um" is NOT the correct ending.

Sorry old chap.. "Reductio ad absurdum" IS the correct spelling. I'll
take the Oxford English Dictionary over you every time..

spino...@my-deja.com

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
In article <90hmu2$6s1$1...@eeyore.INS.CWRU.Edu>,

I'm not going to waste my time on this discussion. The far more
serious error was calling the LOGICAL technique of reduction to
absurdity a RHETORICAL technique, which showed that naisbodo did not
know what he was talking about.

As I said, I know a "little" Latin, and if anything's irrevelant to
software, it's a dead language. Because of the triviality of this
issue, I trusted my memory, and the fact that absurdum looks incorrect,
based on my (two years of high school Latin.)

But what really enrages me is taking a vote amongst a community of
people who regularly misuse the English language and whose hatred of
language is evident in their hatred of precision and charity, which
they are pleased to call verbosity.

It is evident that the professional cowards in this group would rather
spend their time on REAL pedantry rather than discussing software
engineering.
>
> <N/>

spino...@my-deja.com

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
In article <snvp2tso3l8hrcgde...@4ax.com>,
je...@jakfield.xu-netx.com wrote:> Sorry old chap.. "Reductio ad

absurdum" IS the correct spelling. I'll
> take the Oxford English Dictionary over you every time..

I was wrong on this minor issue, and thanks for what appears to be an
authoritative reference. The important error was that reductio is a
logical technique and not a rhetorical technique at all. Furthermore,
naisbodo's spelling did get "reducto" wrong.

spino...@my-deja.com

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
In article <m3itp1o...@mindspring.com>,
Greg Menke <gregm-n...@zxy.mindspring.com> wrote:
>
> The Dept. of Energy has had a similar experience with PeopleSoft. "6
> months" was the first quote- at the end of which, the system couldn't
> generate the first of the important reports. Its been about 3 years
> now, so I imagine its probably gotten somewhat better, but I'd be very
> surprised indeed if the new system is actually operating. So thats 3
> years of paying a bunch of $200/hr people to learn requirements and
> implement them- and thats before you add the incidental support costs
> of trying to get Windows to work reliably. "COTS" indeed.
>
> A complete rewrite of the system by the mainframe systems people who
> had been maintaining it would almost certainly be substantially
> cheaper, not to mention easier.
>
> Gregm

Hey, thanks for the insight. I should just ignore Al Dunbar and
naisbodo, for after all my original post (a review of Steve McConnell's
After the Gold Rush) had as its purpose not a flame war but instead a
serious discussion. However, "flaming" is relevant for oral "flaming"
often disrupts structured walkthrus: PJ Plauger pointed out in 1995
that many development teams can't conduct rational meetings because of
oral "flaming."

A former coworker at Princeton Univ reports the same problems with
Peoplesoft.

I think the problem for public agencies and universities is that their
in-house developers simply won't work absurd hours to make unreasonable
deadlines. The higher level administrators buy in to the ideology that
the private sector is better at everything it does, with the result
that they tend to prefer packages written by and for the private sector
which are insensitive to the culture of government and education.

For example, when I rewrote Roosevelt Univ's (Chicago) grading system
in the early 1970s, I was able to code exception logic to accomodate
demands at the time for pass-fail and other nonpunitive grading
systems. My son's high school, on the other hand, uses a very rigid
commercial system based on traditional As through Fs and thereby forces
classes (such as art or dance) which should not be graded in this way
into a silly and punitive model.

However, the attitude among administrations is that their in-house
programmers can't program. What they mean, I think, is that they
cannot produce acceptable results in a predefined time frame. However,
your experience and that of Virginia shows clearly that packages don't
really solve this problem. Adapting a sufficiently general package is
itself programming and it often involves learning bizarre new languages
which the developers of the package believe to be "4th generation" but
which are, upon examination, pidgin variants of Basic.

In many cases, the corporations developing these packages never
realized that they were in the compiler development or language design
business at all, and as a result hired junior developers to design the
pidgin and to write the compiler.

One solution would be to hire honest developers and allow them whatever
time is needed to develop a quality system. Perhaps if businesses
simply tested developers for honesty and work ethic (which would not be
the same as pulling a credit report, for many people don't pay their
bills because they can't pay their bills) they'd get people who would
not intentionally pad schedules.

Richard Heathfield

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
[Ah, I said my previous response would be my last in this thread.
Well, I lied...]

spino...@my-deja.com wrote:
>
> In article <90hmu2$6s1$1...@eeyore.INS.CWRU.Edu>,
> nx...@po.cwru.edu wrote:

> I'm not going to waste my time on this discussion.

YOU started this sidetrack by incorrectly correcting someone
else's spelling.

> The far more
> serious error was calling the LOGICAL technique of reduction to
> absurdity a RHETORICAL technique, which showed that naisbodo did not
> know what he was talking about.

naisbodo does indeed know exactly what he's talking about;
reductio ad absurdum can be used rhetorically, even though it's a
logical device.

>
> As I said, I know a "little" Latin, and if anything's irrevelant to
> software, it's a dead language.

Weasel words. If you think it's irrelevant, why bother to
"correct" someone else's use of it? Furthermore, if you only know
a little Latin, why did you "correct" naisbodo without checking
your facts first, and why did you defend an incorrect position so
stridently?

> Because of the triviality of this
> issue, I trusted my memory, and the fact that absurdum looks incorrect,
> based on my (two years of high school Latin.)

You were told you were incorrect. Rather than look up the facts
at that point, you reacted to that information by denying that
you were incorrect, until someone had to quote the OED at you.
Finally, you've admitted you're wrong. You could have saved
yourself some credibility by accepting this minor setback earlier
- in fact, you could have shrugged your shoulders and said "Oh
yes, sorry, naisbodo, I was wrong about that", and everyone would
have forgotten all about it. Because you were not prepared to
accept the possibility that you might have been wrong, however,
you have let your mistake blow up out of all proportion and
become a major blow to your credibility. Don't ever run for
office.

The weasel words don't stop there, of course - now that you have
had to admit you were wrong, you opine that the issue is too
trivial to mention.

You're right that it's too trivial to mention, so why on Earth
did you risk your credibility on it? Now that you've been shown
to make incorrect assertions, every assertion you have made is
called even more into question than might otherwise have been the
case.


> But what really enrages me is taking a vote amongst a community of
> people who regularly misuse the English language and whose hatred of
> language is evident in their hatred of precision and charity

You mean clarity.

You see, I don't hate precision or clarity. (If it comes to that,
I don't hate charity either.)

No vote was taken here, by the way, so I don't understand that
reference.

When it comes to regular misuse of the English language, you are
no slouch yourself. I am not one for picking holes in people's
spelling on Usenet, but I've made an exception in your case
because you are like a pot hurling inflammatory accusations at
kettles.

I invite comparisons between your use of English and mine, from
anyone so terminally bored as to still be reading this
discussion.

>, which
> they are pleased to call verbosity.

You are trying to claim that you write with precision and charity
(or, rather, clarity). You have failed on both counts, and it's
time to throw in the towel.

>
> It is evident that the professional cowards in this group would rather
> spend their time on REAL pedantry rather than discussing software
> engineering.

On the one hand, you say that people hate precision, yet on the
other hand you accuse them of pedantry, which you seem to imply
is a bad thing, even though a pedant's aim is precision.

I think you need to take a long, cool shower and have a good
think about whether you are in favour of precision or not.

If you decide you do like precision after all, then you'll be
ready for a discussion on software engineering, at which point we
will, once more, be on topic.

spino...@my-deja.com

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
In article <yzqwvdh...@selena.compugen.co.il>,
Ariel Scolnicov <ari...@compugen.co.il> wrote:
> spino...@my-deja.com writes:
>
> [...]
>
> > Note the epistemological crisis Al has undergone, for he confessed
to a
> > vague disquiet. But the crisis is resolved by marginalizing the
> > messenger and thus old Al is all relieved, for it's basically
harder to
> > question institutional power than to marginalize an individual.
>
> Eschew sesquipedilianism!

Let's take this word by word, and I will justify the use of each
goddamn word.

"Epistemological": the word was used because part of the problem is
knowing that we know, and epistemology is the theory of
knowledge. "Software engineering" is among other things the assertion
that programmers don't know what they think they know, and have little
of value to bring to the table.

"Marginalization": this is the name for not so much dissing an
individual as treating his concerns as a "non-starter": something not
on the agenda. Programmers often think their concerns are critical but
their managers dismiss them as "academic." An example from politics
was Dave Parnas' concerns about Reagan's Star Wars effort, which was
largely software.

Parnas, based on his programming experience, thought he knew that large
systems NEED "live" testing with real data, but a live test of Star
Wars would have involved asking the Russkies, "please, toss some real
nuclear weapons at the United States. We need to live test our missile
defense. Thank you."

Parnas' opponents treated his concern as not on the agenda for their
claim (represented by heavy intellectuals like Tom Clancy) was that the
Software Engineering Institute had devised some real cool techniques
for writing software without having to test it.

Parnas was marginalized and his concern was not even on the table, for
the simple reason that his concerns destroyed the ability to proceed
with Star Wars and they threatened the careers of people invested in
Star Wars.

Literary criticism and philosophy give people back an ability to dialog
with software engineering, simply by providing, not
only "sesquipedelian" words but by defining them in a network. The
only alternative to "sesquipedelian" words is to mutter and to
drool...while carrying out the orders of the top men.

It is said to be Orwellian "Newspeak" to use too many fancy words.
What's interesting is what George Orwell actually wrote about Newspeak
in 1984. Newspeak, in his book, was an attempt not to INTRODUCE fancy
new words but the reverse, and attempt to destroy the ability of Party
members to talk about unsafe topics. To be reflexively anti-big-words
can easily become part of that which would silence discussion.
>
> [...]
>
> --
> Ariel Scolnicov

donald tees

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
spino...@my-deja.com wrote in message <90j8ct$cb8$1...@nnrp1.deja.com>...

>But what really enrages me is taking a vote amongst a community of
>people who regularly misuse the English language and whose hatred of

>language is evident in their hatred of precision and charity, which


>they are pleased to call verbosity.

Now you sound like a ten year old stamping their foot. Ten people take you
to task for using language that is almost impossible to read, and you rant
that this is evidence of hatred of language, throwing in charity for good
measure. More likely it is evidence of a love of language, and you are too
egocentric to be able to understand or accept it.

As to charity, I have seen none from you regarding other people. What I
have
seen is claims by yourself that you love the great unwashed masses, but
think you are too intelligent to stoop to their level. This said with great
outpourings of verbosity. You do not like to hear other people's opinions,
you refuse to respond except in argument, and you think most other people
stupid in comparison to yourself. This is charity? I'll believe you
charitable
when I hear you have done something charitable, not when you spew
disdain, claiming it is out of a sense of charity and love. Normal people
have not fallen for that line since the inquisition.

I have never been a fan of "software engineering". I think it works very
well
when doing a re-write, as most parameters are known by the time of a
second or third design. However, for original systems, often the act of
coding
is the only way that all the parameters can actually be found. Certainly
the act of coding usually leads to a far greater understanding of the
system ... to refuse to accept that understanding and modify a design
accordingly is not going to improve quality, though it may improve speed.

Language can be used to express thought. It can also be used to obscure
real meaning in a vain attempt to garner status, or to obscure the fact that
there is little real substance behind the words. I am still under the
impression
the the latter is your motive.


Jason Che-han Yip

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
<spino...@my-deja.com> wrote in message
news:90jf3q$inv$1...@nnrp1.deja.com...

> In article <yzqwvdh...@selena.compugen.co.il>,
> Ariel Scolnicov <ari...@compugen.co.il> wrote:
> > spino...@my-deja.com writes:
> >
> > [...]
> >
> > > Note the epistemological crisis Al has undergone, for he confessed
> to a
> > > vague disquiet. But the crisis is resolved by marginalizing the
> > > messenger and thus old Al is all relieved, for it's basically
> harder to
> > > question institutional power than to marginalize an individual.
> >
> > Eschew sesquipedilianism!
>
> Let's take this word by word, and I will justify the use of each
> goddamn word.

"confessed to a vague disquiet"?

<snip>


> knowledge. "Software engineering" is among other things the assertion
> that programmers don't know what they think they know, and have little
> of value to bring to the table.

Although I suspect some SE types have this belief, it's definitely not part
of any official definition I've seen nor a universal belief. To keep it
simple: Engineers use technology to solve economic problems. Software
engineers use software technology to solve economic problems. That's it.
The software engineering "movement", if you want to call it that, is an
effort to organize our knowledge about what we do so that it can be shared,
tested, and improved upon.

<snip>


> Literary criticism and philosophy give people back an ability to dialog
> with software engineering, simply by providing, not
> only "sesquipedelian" words but by defining them in a network. The
> only alternative to "sesquipedelian" words is to mutter and to
> drool...while carrying out the orders of the top men.

You seem to be saying that the only way to influence the "software
engineering" movement is use big words. Well, I'm a graduate student in a
"software engineering" program and I can tell you that your sesquipedalian
words don't make me want to dialog at all. In fact, I doubt that any paper
using sesquipedalian words in your style would ever get published in any
peer-reviewed journal. There's a tradition in engineering and engineering
writing: KISS.

The most controversial topic in "software engineering" right now is Extreme
Programming (XP) and and other lightweight methodologies. That crowd also
doesn't use sesquipedlian words but rather a more conversational style. In
fact, there's a phrase from XP: Do The Simplest Thing That Could Possibly
Work.

> It is said to be Orwellian "Newspeak" to use too many fancy words.
> What's interesting is what George Orwell actually wrote about Newspeak
> in 1984. Newspeak, in his book, was an attempt not to INTRODUCE fancy
> new words but the reverse, and attempt to destroy the ability of Party
> members to talk about unsafe topics. To be reflexively anti-big-words
> can easily become part of that which would silence discussion.

You do realise that 1984 was a novel and not a historical account?

In any case, let's look at examples:

Example:
Sesquipedalian - Long and ponderous; polysyllabic.

Why not just use "polysyllabic" or better yet "long"? Does it change the
accuracy of the communication? No. Does it change the ease of
communication? Yes.

No one said that you should be inaccurate.

Jason Che-han Yip

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
"donald tees" <don...@willmack.com> wrote in message
news:90jepr$rpk$1...@news.igs.net...
<snip>

> I have never been a fan of "software engineering". I think it works very
> well when doing a re-write, as most parameters are known by the time of a
> second or third design. However, for original systems, often the act of
> coding is the only way that all the parameters can actually be found.
Certainly
> the act of coding usually leads to a far greater understanding of the
> system ... to refuse to accept that understanding and modify a design
> accordingly is not going to improve quality, though it may improve speed.

<sigh> Why do you believe that "software engineering" does not include
coding? And why do you believe that processes would not adapt to the
situation at hand? If the act of coding is the most efficient way to
greater understanding, why would any sane engineer choose a less efficient
way?

On the other hand, I know of at least one "software engineering" text book
that has absolutely nothing about coding whatsoever, so I guess this IMHO
idiotic view of "software engineering" is out there.

Jason Che-han Yip

unread,
Dec 5, 2000, 3:00:00 AM12/5/00
to
<spino...@my-deja.com> wrote in message
news:90hjd2$3ec$1...@nnrp1.deja.com...

<snip>


> Many programmers who questioned software engineering are driving cabs
> because they were forced out of the business.

Are you sure they didn't just become consultants? :-)

> The real revolutionary wears a suit and tie, like Malcolm X, and, like
> Malcolm, calls on his followers to act with the same dignity as the

I'd agree with the acting with dignity but I hope you don't expect the
average software developer, or engineer for that matter, to start wearing
suits and ties...

> ruling elite. My claim is that the high-tone talk of "science" in
> software engineering needs to be met, not with inchoate muttering and
> drooling, but with even higher-toned analysis of its cultural and
> scientific origins.

"vague" would have been simpler than "inchoate" but it can work...

Don't know what you mean by "high-tone". If someone comes with you with
"science", you should know what they are talking about, yes. No idea why
you'd need to be considering cultural orgins.

> Here's an example. Suppose you are asked to write a report by your
> manager and the manager tells you it is too long, and quotes Polonius'
> speech in Hamlet, where Polonius admonishes Laertes not to use too many

Has anyone actually had a manager quote Hamlet to them?

> words. It is a common management technique in engineering, for the
> manager to show that he has more humanities cultural depth: women
> managers are especially fond of this.

No engineering manager I've ever met has tried to pull this and I doubt any
engineer would be impressed.

> But if you actually read Shakespeare (or rent Ken Branagh's excellent
> movies) you can come right back with the fact that we need not take
> Polunius' advice, for it's obvious Shakespeare thought Polonius was a
> damnfool, and Polonius, in a later scene with Gertrude, himself is
> overly prolix. Shakespeare, who used far more words than the average
> playwright of his time, had no brief for terseness for its own sake.

My only answer is please look up a book on technical writing. Neither
managers nor engineers have time to read 5 act plays when all they need is a
status report.

spino...@my-deja.com

unread,
Dec 6, 2000, 1:00:59 AM12/6/00
to
In article <3A2CC5D9...@antlimited.com>,

Richard Heathfield <ric...@antlimited.com> wrote:
> [My last article in this thread]
> > >
> > > F = ma (from Newtonian mechanics)
> > > E = mcc (from relativity theory - sorry for the absence of
> > > subscripts...)
> >
> > This is a nonsensical example,
>
> No, it isn't.
>
> > for anyone who knows only that f=ma or
> > even the words "force equals mass times acceleration" or "energy
equals
> > the speed of light squared times mass" knows neither general
relativity
> > nor Newtonian mechanics AT ALL.
>
> Very true, but the example is not nonsensical because it demonstrates
> how complex ideas can be expressed simply, which was the point. I did
> not and do not claim that these expressions suffice for a full
> understanding of the entire subjects in which they are relevant.
>
> Read for comprehension, sir.

Richard, the discussion (which is wearisome but in which I persever
because it is germane to software) was whether the original post, a
review of Steve McConnell's book AFTER THE GOLD RUSH, was verbose.

Verbosity depends on the needs of the audience.

At the end of a physics lecture where the professor explains clearly,
in as many words as it takes, Newtonian mechanics or relativity, he may
indeed triumphantly write either of your equations on the board and the
students who get it may indeed say, aha, how simple, how elegant, and
how unlike those goddamn wordy philosophers.

The problem is that the real message is the content of the physics
lecture, as well as the students' preparation in the form of reading
the required chapters. The simplicity of f=ma does not aid the student
who does not know why force equals mass times acceleration.

You can only judge a statement simple when you know it to be TRUE:
truth precedes simplicity: a false but simple statement is useless.
But the literary critics *manque* of this thread, prior to judging the
truth of my assertions concerning software engineering, judged their
complexity.

f=ma is at best an elegant slogan. Now, the problem with sloganeering
in more value-laden fields like software engineering is that the slogan
admits of too many counterexamples from praxis whereas scientific
slogans are just TRUE and admit of no counter-examples.

For example, one of Steve McConnell's slogans is "design before code."
This is presented as a Great and Simple Truth. But it completely
ignores the technique of prototyping, part of Rapid Application
Development, and part of software engineering.

Overemphasis on simplicity keeps software engineering and other
sciences of man content-free for it its literally true that the student
can not learn anything (simple or complex) on which he can rely. This
is probably the reason for the fact that students who pay thousands of
bucks for classes in software engineering have discovered, at a
probably higher rate than "real" engineers, that the practices they
learn in university simply are not used in industry.

But were I to say, "software engineering = bullshit squared", this
would be uncharitable, if not verbose, and disproved by the real
contributions of software engineering.

I have instead to use, as a layperson, something like Diane Vaughn's
methodology in her book THE CHALLENGER LAUNCH DECISION. Vaughn in
order to be accurate engages in "verbose" anthropological thick
description in order to find out what really happened in this
disaster. She disproves Feynman's oversimplified assertion that the
middle managers at NASA and Morton Thiokol "ignored the laws of
nature." Instead she finds that institutional pressures to meet
schedules, directly related to the politics of the goddamn Reagan
administration, were at fault. Her "verbosity", if that is what it is,
is simply of higher quality than Feynman's sloganeering.

In addition, I am trying to introduce the very strange notion of
software engineering as literature, as a form of writing, into a
community that has not read Foucault or Derrida. The onus on me is
therefore to be "verbose" and EXPLAIN as best I can the meaning of
cultural references. For example, I've explained "Foucauldian moments"
where popular anti-intellectualism and the laughter of nervous children
implement structures of power.

>
> >
> > This is like the manager who writes down phrases in a meeting and
> > passes them along as knowledge to programmers, without finding what
the
> > phrases mean.
>
> No, it's more like programmers being able to communicate complex ideas
> in conversations like:
>
> "What's the best way to store these IPs? Tree or hash?"
> "Use a hash - quicker, less RAM".
>

Good example. But this exchange takes place in a Wittgensteinian
language game that inherits all sorts of unspoken assumptions,
including the knowledge of the programmers how to implement trees and
hash arrays: not all programmers have this knowledge. It also assumes
that you would like to reuse the IPs as units, and not analyze them to
see if they have elements in common, in which case the "terse" answer
is wrong.

Indeed, it's an interesting example of programming bricolage, which
mistakes the faster for the better IN ALL CASES, and is the reason for
the resentment in this thread of "verbosity." I've seen a number of
data bases that store information which has a structure (like IPs) in
a "fast" way that does not reflect structure at all, resulting in
denormalized data, accessed real fast.

The result is the creation, after the fact, of expensive search
routines which rummage through the "fast" arrays and reconstruct the
needed information, such as the set of all IPs containing "Amazon."

This may be deliberate, for a hierarchical, normalized, "slow"
representation which assigns a node in a tree to each item, or even
better a DAG or directed acyclic graph, which places common
subsequences like Amazon.COM in one place, has a tendency to destroy
the need for coding. The rage for an apparent simplicity, which pushes
the need for code into the future, is a rage, in part, for job
opportunity.

Programmers are artisans who in a truly rational society would be paid
for specific needed works, and, every time those works were used,
programmers would receive royalties which would sustain them in their
old age. But our society, probably because of the felt need to keep
employees under Panopticon supervision lest they goof off, prefers most
programmers to be employees. Because the employee programmers are in
many cases NOT being fairly compensated for their work, given its value
to the firm, they have to play games in order to ensure their
employability, and one of these games is deliberate oversimplification
which creates opportunities for rework.

My personal observation is that programmers who resent "verbosity" and
nuance generally design systems that hammer nuance, complexity, human
relations, and the rain forest into the long grass. They tend to
marginalize "unlikely" cases, bringing the software engineer's
misplaced empiricism into discussions inappropriately, and thus have
been responsible, over time, for a variety of annoyances including 64K
(or 128K, or 16K) limits on the sizes of files.

Your simple example can be an example of a good solution or a bad
solution. Faster isn't always better.


> >
> > So gee Shakespeare should knew how to write, huh?
> ^^^^
>
> Mr Spelling-Bee, huh?
>
> Citing one example of a playwright who expresses some complex ideas in
> complex ways does not prove that all complex ideas must be expressed
in
> complex ways.

Certainly not. The question is whether the typical mistake in
technical and scientific writing is verbosity, or its opposite. My
feeling that when people write, they labor under an unexamined anal-
compulsiveness that generally causes them to err on the side of
terseness. The anal-compulsiveness derives from a society which has
placed the cash metric on their speech.
>
> Read for comprehension, sir.


>
> > The
> > humorist Dave Barry noticed long ago that the Internet is a guy
> > phenomenon, and guys think it prissy to use complex sentence
> > structures.
>
> I am perfectly prepared to read, and indeed to use, complex sentence
> structures, when I consider them to be necessary and appropriate to
the
> point I am making, and likely to be comprehensible to my intended
> readership. If I am writing for a readership which is not experienced
in
> the use of technical jargon, I either won't use any or will define the
> terms I use as I use them. When one is addressing technical newsgroups
> such as the ones to which you posted your article, one cannot sensibly
> assume that one's intended readership is fully conversant with the
> meanings of words like "epistemological". Thus, if one needs to use
such
> a word, one ought to define it.
>

Ah, but then I am "verbose." I suggest your real problem is with the
message, that what poses as Science is not value-neutral. You seem to
cover up this by posing as a literary critic, for this delays and
forestalls any real discussion...of software engineering.

>
> It depends on your intention. If you're seeking to impress, use big
> words and damn the consequences (such as this overly-long thread). If
> you're seeking to inform, consider your audience.
>

I really haven't seemed to impress anyone. Anyone in our society,
which has long ago placed an economic premium on being terse, who seeks
to impress is well advised not to be verbose but instead authoritarian,
and suck up to power while finding some powerless group on which to
take out his anger.

> It strikes me that you're far more interested in impressing people
than
> with informing them, and that you have failed on both counts.
>

Not at all, sporto.

My experience on the Amazon Customer Comment site (which is moderated,
and which rejects unwanted posts) is that typically (not always) a
review of mine is accepted.

Amazon has a rating system in which readers can place their subjective
evaluations of book reviews, and a rather silly contest and chachka
system for rewarding "top" posters with the highest ratings.

My typical experience is to get an extreme number of unfavorable
ratings rather quickly, followed by a steady growth of more favorable
ratings, and email praising the post, over a longer period of time.
Email includes stuff from the authors of the books and job offers. My
theory is that the unfavorable ratings are from people who take one
look at the word count and the word count alone, and decide that the
post is worthless, and ding the "not useful" box.

My purpose is not to impress the people who over time realize the value
of the post. It happens to be communication with a person that has
read and understood it. Now, this purpose may be unrecognized on an
internet just chock full of monads who don't care to communicate, only
to flame.

> >
> > [I do not want to give offense here to Native Americans,
>
> You gave it your best shot, though, didn't you?
>
> > so I switched
> > to a Russian proverb.
>
> Going for the double-whammy?
>

Hell yeah. The more people I can piss off the better.

> > I'll also point out that Native Americans are
> > caricatured by the "silent Indian" image and there is a wealth of
> > stories and songs from Native Americans.
>
> What on Earth has this to do with what we're discussing?
>

Get a clue. American males hate language because they learned that the
cowboy and Indian were "strong and silent." This resentment of
language has in recent years been exported by American dominance,
especially in technical fields.

> > I am talking about the
> > cultural baggage of Internet honchos.]
>
> a) this is Usenet, not the Internet. Usenet can use the Internet, but
> does not have to.

I just love Usenet pedants!

> b) You appear to be making the mistake that many Usenetters do, of
> assuming that everyone in the world is an American, with American
> cultural norms, values, and referents. For example, I'm not entirely
> clear what you mean by a "honcho".
>

Guy in the loop, guy in the know, man in charge, Sarge.

>
> Write for comprehension, sir. Very few people had a clue what you were
> talking about. I've just re-read your original article, and I have to
> say I found it a hilarious exercise. Did you really think that the
> majority of your selected readership would be able to understand, or
> care about, most of what you wrote?
>

The keyword here is "majority." It is probable that the majority of
readers are of a level of intelligence and sensitivity too low to
understand. As I have said, I am concerned with point-to-point
communication through a mass of irrevelant targets. Onward through the
fog.

This is actually a software engineering issue, for software engineering
as a science of man reifies a lowest common denominator and pretends
that we all must be concerned all of the time with the lowest common
denominator. Thus, we are supposed to be impressed with
an "innovation" in SQL Server that means that we no longer have to
remember to use the MoveNext method in looping through a recordset.
Thus Microsoft tells us to "let go, and let MTS" (an almost blasphemous
change to a well-known recovery slogan), because apparently the very
idea of a LIFO stack is an Eleusinian mystery to Windows programmers.

>
> I have no idea what you mean by "cultural button". I'm picturing a
large
> coat-button visiting an art gallery, which obviously isn't what you
> meant.

Nice image. The issue here is of the "hot button." This is the
situation where a listener or reader sees a word (such as writing,
programming, or abortion) that raises, for him, a great deal of
emotional issues. He tends to read things into the prose as a result
of seeing the keyword.

The contention of incompetent writing teachers is that we should avoid
such hot buttons. We should, unless to do so changes the message (the
mistake of incompetent writing teachers and the pretentious critics in
this thread is to think that style should trump truth.)

Writing is a hot button in our society because most people can't form a
grammatical sentence on paper, owing to the "Savage Inequalities" of
our educational system. For this reason, fueled by class resentments
which are unspeakable in our culture because of a prohibition on "class
war", people tend to ignore the beam in their own eye, while pointing
out the mote in the Other's eye. That is, instead of learning how to
read and write they spend their time flaming those who choose to write,
and be damned.

>
> > and to cause the same
> > resentments, as does writing. Many programmers actually
hate "clean",
> > elegant code
>
> I don't know of a single programmer who hates clean, elegant code. You
> obviously mix in different circles to me.
>

OK, I have worked in a variety of different roles.

At Bell-Northern Research in the 1980s, most of the developers were
unix loyalists and concerned to write what we would probably agree is
clean, elegant code. I'd say that in computer-cultural terms, these
developers were the inheritors of the Algol tradition of emphasis on
reusability and the lack of hesitance to use a high level of
abstraction (as in the definition of a statement in C and Algol, in
which compound and atomic statements form a closed set.)

But at various places over time where I have written Cobol and Visual
Basic, a very different culture operates. This culture was formed and
malformed by the dominance of IBM in the period 1960..1985, and the
dominance of Microsoft thereafter. Its ur-language was Fortran. Its
culture is characterized by a lower patience with abstraction (as in
Fortran's definition of statement, which did NOT include a compound
statement.)

The tradition I encountered as Bell-Northern Research (and Princeton)
runs from Algol, to DEC, to Linux. The "business" tradition starts at
Fortran and Cobol and runs through the IBM mainframe, straight to
Windows NT.

Programmers in the business tradition do sometimes dislike elegance,
perceived as a waste of time.

And your snotty comment is part of the problem, for the problem is
social class and the Savage Inequality of our educational system. At
Stanford, compsci students are prepared for a professional career in
which they can afford to be snobs. At state and third-tier schools,
students are tracked into a lifetime of struggle with second-rate
systems. The latter eventually reconcile themselves with grunge by
falling in love with grunge, and their hatred of inequality is
marshaled for technically Fascist ends.

Students for a Democratic Society, in the 1960s, called
this "tracking", and they were RIGHT. Programming education is sharply
divergent, and, at the lower levels, teaches more ideology than
technology, especially the ideology of management control. Yet my
discovery while teaching at DeVry was that a clear explanation of a
Turing machine was just as accessible and exciting to DeVry students as
it was to coworkers at Princeton.


> > because it is a cultural reproof to their self-perceived
> > lack of ability,
>
> I also don't know any programmers with a self-perceived lack of
ability.
> The opposite problem is more usually the case.
>

I am sure you are familiar with the bluster that covers up insecurity.

> > and their unspoken anxieties about whether they really
> > belong in the programming racket at all.
>
> If they are unspoken, how can you know that these anxieties exist?
>

I'm a sensitive kind of dude, OK?

>
> My dear chap, the proposition was that complex ideas cannot be
expressed
> simply, and I have defeated it. I have not said that all complex ideas
> can be expressed simply, and I have not said that an entire scientific
> discipline or even sub-discipline can be summed up in one equation. I
> have merely pointed out that equations are a good way to express
complex
> ideas simply, thus defeating your proposition.

Oh, gee, that's useful. I need to use symbolic logic to express my
thoughts.
>
> Read for comprehension, sir.
>
Bite me.

> Sometimes you do, and sometimes you don't. When I suggest to a fellow
> programmer that he might consider using a deque as an appropriate
> solution to his problem, I can confidently expect that he will know
what
> I mean, and if he's unfortunate enough not to have met the term, he
can
> ask for clarification, which can be given in a few words - "it's a
> double-ended queue - you can add and remove from either end". I don't
> have to spend huge amounts of time explaining the concept, because he
> already has a good understanding of the field.
>

This is a verbal exchange, where cues let the speaker know that he
should go on. Usenet/Internet is a venue in which the reader is
perfectly free to bail out.

> When you are trying to explain something foreign to your selected
> readership's experience, however, you do need to spend a lot more time
> bringing them up to speed.
>

The very idea that Michel Foucault might have something to say to
software engineers is quite rare, but I thought I was not supposed, by
your rule, to be "verbose."


>
> Just out of sheer curiosity, what led you to believe that your article
> would be of interest to the newsgroups you selected?
>

It's obvious, by the sheer volume of replies, that it is of great
interest.

> > >
> > They think they are measuring because they are geeks
>
> Ah, you'll have to define "geek", I'm afraid.

I am guessing you are British: a geek is a boffin, a chap in a
technical field characterised by perceived lower social skills (which
are very often in the eyes of management beholders, whose
social "skills" would not be skills at all in a just society:
consisting as they do of the skills of the bully and fraud, in signal
instances.)

>
> So, like I said, we "know" intuitively that a 10 MLOC program is more
> complex than a 10 line program, but we cannot know that a 2 KLOC
program
> is more complex than a 1 KLOC program. The second half of the sentence
> indicates that counter-examples can exist; you have pointed out
another
> counter-example - big deal. Nevertheless, in general terms, big
programs
> tend to be more complicated than little programs.

"In general terms" assumes that programs are part of nature and best
subject to empirical analysis. This is a mistake.


>
> No, it's not. It's a heuristic, and a useful one. That's not to say
that
> it's solid enough to base, say, remuneration on (and, indeed, if you
> did, you'd end up with your program where i++ is repeated 10,000,000
> times, human nature being what it is), but it's one indicator of
> complexity. It can't be used alone, and it may not even be a major
> indicator, but it is certainly one of the things one takes into
account
> when looking at code complexity.

"Heuristic" has a root having to do with the lucky or happy
accident. "Heuristic" means that we tried something and found it
rewarding.

But software metrics have significantly FAILED to tell us anything
useful.

You cannot say "I am gonna use a heuristic, for shits and giggles",
have poor results, and then be all proud of your heuristics.

The managerial reification of code and time generally is part of the
problem set. This is because human language is so flexible that
developers and their managers can at any time change the scope of terms
of art to make it look like they are succeeding.

For example, a year ago in the testing of a missile defense software
system, a senior researcher protested the alteration of test records to
make it appear as if the system was working. Her supervisors told the
New York Times that the specifications were "rigid", presumably in a
phallic way. She pointed out that they were easily fudged given the
pressure to demonstrate to the Clinton administration that the United
States need not eliminate nuclear weapons by treaty, but could instead
construct a new form of Star Wars.

When we point to the weakness of the metrics, we immediately expose
their lack of science, but the response is "they are heuristic."
Heuristics, however, are justified only by success. What these metrics
really are, are reification and fetishisation which we learn from the
fetishism of commodities. Just as we do not see the labor that goes
into a pair of running shoes, on the job, we airily dismiss weeks of
real coding as "XYZ" which we "heuristically" know will take one week.
Just as management hand-waving becomes weeks of meaningless work for
actual programmers, the shiny running shoe was weeks of underpaid work
for the Malaysian worker.

> > > can't measure it with a ruler or a balance is neither here nor
there -
> > > we make heuristic judgements of complexity regularly. Sometimes,
> > > therefore, we make wrong judgements. But we get it right often
enough
> > > that we consider it worth continuing to do.
>
> I've left this bit in, even though you didn't reply to it, because I
> think you should have replied to it It is a direct rebuttal of what
you
> said, so I'd be interested to hear your reaction to it.

Here's my reaction. Software engineering uses a prestige borrowed from
the hard sciences but it has produced approximately the SAME number of
disasters as traditional *bricolage*, and meanwhile Open Source
accomplishes things the software engineers cannot.

The Internal Revenue Service has, over the past ten years, used highly
recommended practices of software engineering and failed repeatedly to
meet its goals. Ditto for air traffic control.

NASA, although it uses software engineering methodology, seems in
general to eschew its statistical quality control approach, especially
in manned spaceflight. To the extent it has, its software has been far
more successful than the IRS for the FAA's ventures. For example, the
Pioneer craft, whose software was written before software engineering
was named, has now flown beyond Pluto and will not die.

The problem is that we CANNOT make "scientific" judgements of
complexity when the complexity includes social relations. NASA is more
successful because it works in outer space, where social relations
don't apply except trivially and controllably, as in the crew of the
Soace Shuttle. Whereas the IRS is involved with millions of people who
do not want to pay taxes, and the FAA has to reconcile the demand for
safety with the demand for landing as many planes as possible.

>
> So do I. If you're going to correct people's spelling, get the
spelling
> right yourself.

If another poster's correction is itself OK, then I stand
corrected...but not by you. But your more important mistake was to
call reductio "rhetoric" when it is logic.


>
> At present, your assertion that you are correct is just that - an
> assertion. It has no more validity than mine. If you want to pick
holes
> in people's spelling, a most unUsenettish thing to do (except in
revenge
> for having it done), you'd better be able to prove that your
correction
> is correct, and proof requires more than assertion.
>
> Indeed, it was your incorrect correction of naisbodo's spelling which
> prompted me to send my original reply.
>
> >, and if you think for one fucking
> > minute I am going to take the votes of thousands of mental
defectives
>
> Ah, how revealing. This is how you talk, and how you view your fellow
> Netizens, when you've forgotten you're supposed to be intellectual, is
> it?
>
> > you've got another thing coming.
>
> ITYM "think". If you criticise other people's spelling, be damn sure
> your own is correct.
>

Your correction would not be grammatical, so I suggest we not waste
bandwidth on this gamesmanship.

> > "um" is NOT the correct ending.
>
> Your assertion is meaningless without independent and authoritative
> evidence.
>

It still does not look right to me, but it's been years since I studied
Latin and I've admitted a probable error. What's more important is
that reductio ad abusurdumamwhatthefuck is a valid logical
argumentation technique UNLESS you are a mathematical intuitionist like
Brouwer, not a rhetorical technique at all.

>
> If reductio ad absurdum were not a rhetorical tactic, it could not be
> used rhetorically.
>
> I am using it rhetorically.
>
> Therefore, it is a rhetorical tactic.

You CAN'T use it rhetorically: you can only use RAA logically, and
either validly or invalidly. And, if you are an intuitionist who
denies the validity of the law of the excluded middle, you can't use it
at all.

>
> I'd have thought it showed a healthy respect for people's ability to
> select newsgroups and academic subjects in which they are interested.
> Fascism (in the strictly accurate sense of that word) is not a topic
> which one goes looking for in programming newsgroups; those in your
> audience who don't know what Fascism really is (and I'll bet it's most
> of them) /don't care/ what Fascism really is; otherwise, they'd have
> gone and found out. Those few who do care either will go and find out
> now, or have already found out and therefore already know.
>

That's my entire discovery. The reason why Americans consistently seem
to fail at writing truly great software is because our culture is
pervaded by fetishization, reification, and, to a degree, by the
Fascist mobilization of wounded souls against false targets, including
midlevel intellectuals...even in math and science.

Now, it is true that Communist Russia was not all that better at
writing software. A. P. Ershov's group in the 1960s seems to have
failed to write a compiler for Algol 68 just like everybody else, and
of course the bureaucratization and centralization of Soviet life was
inimical to software creativity. However, I did notice as a teacher of
C in the early 1990s that Russian students were significantly better at
coding than Americans, in part because of the discipline enforced by
scarce and centralized computer time.

The Soviets never analyzed how modern culture itself drives us into
self-defeating patterns of thought and behavior. They mobilized anger
against intellectual production and any "verbosity" except Party
speeches (Ayn Rand's mother was attacked on a train, for reading a
book, during Lenin's time: she was thought to be "bourgeois.")

But societies like Finland and Germany with respect for engineers have
produced some striking successes because their developers haven't been
under the American cultural regime of management control, Taylorism,
anti-reinvention-of-the-wheelism, and the fetishization of commodities.

For this reason, I think there is a space for a critical, left software
engineering BEYOND hippie programming. The problem is that it would
radically alter large institutions...rather than, in the American
cultural tradition, simply retire to Montana with a modem.

spino...@my-deja.com

unread,
Dec 6, 2000, 3:00:00 AM12/6/00
to
In article <90jnqs$1cus$1...@nserve1.acs.ucalgary.ca>,

"Jason Che-han Yip" <j.c...@computer.org> wrote:
> <spino...@my-deja.com> wrote in message>
> Although I suspect some SE types have this belief, it's definitely
not part
> of any official definition I've seen nor a universal belief. To keep
it
> simple: Engineers use technology to solve economic problems. Software
> engineers use software technology to solve economic problems. That's
it.
> The software engineering "movement", if you want to call it that, is
an
> effort to organize our knowledge about what we do so that it can be
shared,
> tested, and improved upon.

For whose benefit?

>
> <snip>
> > Literary criticism and philosophy give people back an ability to
dialog
> > with software engineering, simply by providing, not
> > only "sesquipedelian" words but by defining them in a network. The
> > only alternative to "sesquipedelian" words is to mutter and to
> > drool...while carrying out the orders of the top men.
>
> You seem to be saying that the only way to influence the "software
> engineering" movement is use big words. Well, I'm a graduate student
in a
> "software engineering" program and I can tell you that your
sesquipedalian
> words don't make me want to dialog at all. In fact, I doubt that any
paper
> using sesquipedalian words in your style would ever get published in
any
> peer-reviewed journal. There's a tradition in engineering and
engineering
> writing: KISS.
>

I am not doing engineering, instead I am doing the critical theory of
engineering. I am probably not even qualified to publish papers in
your journal. I make this (surprising) admission because on principle
I have refrained from learning too much about the unnecessary and
pernicious parts of software engineering.

> The most controversial topic in "software engineering" right now is
Extreme
> Programming (XP) and and other lightweight methodologies. That crowd
also
> doesn't use sesquipedlian words but rather a more conversational
style. In
> fact, there's a phrase from XP: Do The Simplest Thing That Could
Possibly
> Work.

This is a good example of ideology. As a rule of thumb, The Simplest
Thing That Could Possibly Work, is excellent. But as soon as "extreme
programming" receives an acronym and becomes a shtick, it is used in a
fashion reversed from its original, liberating charter, and is used to
terrorize people and users who don't want The Simplest Thing That Could
Possibly Work.

Galileo himself, while part of Renaissance science, was no fan of
simplicity for its own sake. Charged with excessive writing style,
Galileo wrote that that which gives "grandeur, nobility and excellence"
to writing is the extras.

>
> > It is said to be Orwellian "Newspeak" to use too many fancy words.
> > What's interesting is what George Orwell actually wrote about
Newspeak
> > in 1984. Newspeak, in his book, was an attempt not to INTRODUCE
fancy
> > new words but the reverse, and attempt to destroy the ability of
Party
> > members to talk about unsafe topics. To be reflexively anti-big-
words
> > can easily become part of that which would silence discussion.
>
> You do realise that 1984 was a novel and not a historical account?
>

Can't you read? I use 1984 as the title of the book, not the year in
which Orwell was long dead, and Blondie was young and hot. To help you
along, I then used, in my verbose way, the phrase "in his book."

The problem may not be verbosity. It may be engineers' functional
illiteracy.

> In any case, let's look at examples:
>
> Example:
> Sesquipedalian - Long and ponderous; polysyllabic.
>
> Why not just use "polysyllabic" or better yet "long"? Does it change
the
> accuracy of the communication? No. Does it change the ease of
> communication? Yes.
>

That was not my word. Another poster used it to satirize his (half-
comprehended) reception of my style.

Like it or not, Latin influenced English, and it is racist to censor
the use of Latin based phrases.

donald tees

unread,
Dec 6, 2000, 3:00:00 AM12/6/00
to

spino...@my-deja.com wrote in message <90lqdj$f2q$1...@nnrp1.deja.com>...

>
>Like it or not, Latin influenced English, and it is racist to censor
>the use of Latin based phrases.
>

Racist? Bullshit. It has been a long time since being anti Latin
was racist.

It is loading more messages.
0 new messages