Re: [AM] Let's call a spade a spade

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Are you looking for savings on products you use everyday?=20
Visit Quality Health today and see the coupons, free=20
samples and special offers our members enjoy each and=20
everyday.
http://click.topica.com/=
caab5n1bUrKDAbWnbtka/ Ivo Interactive
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

 I agree about OO implementation, it has ended up as the aim rather than th=
e
tool.

 But has not OO suffered the same as Agile is suffering - the intent is los=
t
in a cacophony of words. Words from people who know no more than the words
themselves - with no internal model which allows differentiation between
software choices, usually managers who left their technical areas too early=

in the pursuit of success and prestige.

 After OO was implemented in C and other mainstreams from models like Eiffe=
l
and Smalltalk, the masses believed that OO was fully defined and implemente=
d
by that model. But before those implementations manifested, the CONCEPT of
OO was being discussed and pursued by small groups, usually in software
bureaux, where conventional development was not an option. The now accepted=

definition of OO is one of the many ways the concept could have (and has)
manifested.
 I always have had trouble with the OO implementations. I found them less
effective than the techniques I was currently using, and still use. One day=
,
in the late 80's, I asked a fresh graduate whether he could summarize what
he understood of OO. His answer was "What, not how". I really like that
answer.
 Is that not also at the essence of Agile? Manage the technical in such a
way that there is a beneficial interaction between user and developer? What=

am I doing, not how will I implement this.



----- Original Message -----=20
From: "Rick Lutowski" <[email protected]>
To: <[email protected]>
Sent: Sunday, March 28, 2004 2:58 AM
Subject: Re: [AM] Let's call a spade a spade


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Are you looking for savings on products you use everyday?
Visit Quality Health today and see the coupons, free
samples and special offers our members enjoy each and
everyday.
http://click.topica.com/caab5n1bUrKDAb7u5T4a/ Ivo Interactive
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

debhart wrote:
> I'm trying to work out where (or how?) to draw the line myself...


We are about to go on a journey through time and space...

The time is now 1984. The space is an alternate universe
in which the Agile Manifesto was written in 1979. These
messages are all dated 1984 and are being written in the
context of 1984 software technology.


There is this new thing people are talking about. Something
about designing software using objects.  Others are talking
about hiding information.  Sounds dumb to me -- as a
software maintainer I need more info, not less.  People
are supposed to interact, not hide things from each other!
And this thing about designing subroutines to represent
objects sounds very unnatural; everyone knows a subroutine
represents a good 'ol function.  Thinking so unnaturally
violates the simplicity principle.  And of course, our
customers will never understand it, even if us developers
somehow manage to figure it out.  That makes customer
collaberation a lot harder.

So what do we have? Info hiding instead of open interaction,
unnaturally complex code structure, confusing design that
makes cummunication with the customer harder -- this whole
object thing violates a whole slew of our values. I think
us agilers should be against this new object craze as it
clearly is not agile.

What do you think?


..Control of time and space is now being returned to you.

--=20
Rick Lutowski
Principal, JReality
[email protected]
http://www.jreality.com

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Menthol Smokers Only! Click on the link below and
register to receive up to $50 in savings from one of
America's leading menthol brands.
http://click.topica.com/caab4S3bUrKDAb7u5T4f/ Lorillard
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

For more information about AM, visit the Agile Modeling Home Page at
www.agilemodeling.com

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
**** Bounces like rubber! Shatters like ceramic! ****
Discover Crazy Aaron's Thinking Putty in grown up=20
handfuls. It's the creativity unleashing, mood enhancing=20
desk toy!
http://click.topica.com/=
caab5n2bUrKDAbWnbtkf/ Crazy Aaron Enterprises
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

For more information about AM, visit the Agile Modeling Home Page at www.ag=
ilemodeling.com
--^----------------------------------------------------------------
This email was sent to: =
[email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.=
bWnbtk.=
Z2NtYS1h
Or send an email to: [email protected]

For Topica's complete suite of email marketing solutions visit:
http://www.topica.com/?p=3DTEXFOOTER
--^----------------------------------------------------------------