[Reply]
HI Berend,
At 07:43 on 31/07/2008 you wrote
>To : delphi@delphi.org.nz
I agree to the point regarding the example of the Medical profession, where it
is totally dominated by the Pharmaceutical industry as well - but at least
someone calling themselves an MD for the most is found to
> "Gary" == Gary T Benner <[EMAIL PROTECTED]> writes:
Gary> Like funeral directors, who need no formal qualifications,
Gary> anyone can buy a copy of Delphi, VS, or whatever, and call
Gary> themselves a software developer, software engineer, or
Gary> software architect ( if the
Yes, there a heaps of cool Ted talks, I've watched quite a few now.
Alister Christie
Computers for People
Ph: 04 471 1849 Fax: 04 471 1266
http://www.salespartner.co.nz
PO Box 13085
Johnsonville
Wellington
Neven MacEwan wrote:
> http://www.ted.com/index.php/talks/james_howard_kunstler_dissects
Well I would say a "Software Architect" must be an order of magnitude
higher than a "Software Engineer", given the lowly status of engineering
in NZ.
Todd.
> Steve
>
> As my father was fond of saying (When we agreed ) "Great minds think
> alike" followed by "Fools seldom differ"
>
> Thanks for
e that is required in such an app, but
> IMHO you're
> > > comparing apples with oranges.
> > >
> > > RAD does not lend itself to larger apps which are
> intended to be
> > > easily maint
such an app, but IMHO you're
> > > comparing apples with oranges.
> > >
> > > RAD does not lend itself to larger apps which are intended to
> be
> > > easily maintainable and intended to be worked on by a team of
> >
> > developers.
> >
> > Cheers,
> >
> > C.
> >
> >
> --------
> > *From:* [EMAIL PROTECTED]
> <mailto:[EMAIL PROT
EMAIL PROTECTED] On
Behalf Of Neven MacEwan
Sent: Wednesday, 30 July 2008 10:09 a.m.
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] OO Programming
Steve
So what we need is OO RAD? Where you define classes and they 'instantly'
appear on your palette (and are dynamically
pp, but IMHO you're
>> comparing apples with oranges.
>>
>> RAD does not lend itself to larger apps which are intended to be
>> easily maintainable and intended to be worked on by a team of
>> developers.
>>
>>
.
> >
> > RAD does not lend itself to larger apps which are intended to be
> > easily maintainable and intended to be worked on by a team of
> > developers.
> >
> > Cheers,
> >
> > C.
> >
> >
> ---
t; C.
>
>
> *From:* [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> [mailto:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>] *On Behalf Of *Steve Peacocke
> *Sent:* Wed
*On Behalf Of *Steve Peacocke
> *Sent:* Wednesday, 30 July 2008 8:13 a.m.
> *To:* NZ Borland Developers Group - Delphi List
> *Subject:* Re: [DUG] OO Programming
>
> Just an interesting observation - why do people think that RAD
>
[Reply]
Hi all
At 09:24 on 30/07/2008 David wrote
>Also, ModelMaker is an invaluable tool to help visualise OO code and how
>the various parts fit together.
I, like, the Russians in the early days of the space race, still use a pencil!
cheers
gary
Ref#: 41006
_
My approach depends on the project.
For quick, cheap and cheerful projects, or utility style applications I
use RAD. For mid size projects I always use an OO approach. I've had good
luck with InstantObjects.
Also, ModelMaker is an invaluable tool to help visualise OO code and how
the various p
> >From my POV, RAD is generally taken to mean what the acronym stands
> >for,Rapid Application Development; i.e. drop some components on to a form,
> >wire up a few event handlers, voila.
>
> RAD does not lend itself to larger apps which are intended to be easily
> maintainable and intended
> RAD is a methodology, OOP is a programming style.
>
>
Thanks Steve, I was wondering too. I think the OP has something specific
in mind.
--
Phil Scadden, Senior Scientist GNS Science Ltd 764 Cumberland St,
Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232
Notice:
d on by a team of developers.
Cheers,
C.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Steve Peacocke
Sent: Wednesday, 30 July 2008 8:13 a.m.
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] OO Programming
Just an interesting
Just an interesting observation - why do people think that RAD programming
excludes OOP programming?
RAD is a methodology, OOP is a programming style.
Steve
http://stevepeacocke.blogspot.com/
___
NZ Borland Developers Group - Delphi mailing list
Post: d
Same as most of the others on the list. A bit of both. RAD, Data Bound
stuff for simple edit screens and reports, but OO structure for more
complex screens and processes. Even the simple edit screens are based on
top of a few useful base classes that do most of the grunt work.
Stacey
-Origina
My older code is RAD style. I have a 14 year old application with 500k+
lines of code that I still maintain and extend without too much pain.
All my newer stuff uses the ti object persistence framework (tiopf.com). it
takes a bit more work to get started but results in better code.
Regards
Sea
[Reply]
HI Alister,
Horses for courses.
Many programmers on this List work on just one or two large projects, in which
case it is a no-brainer to use OO.
On the other hand, many others are involved with many smaller projects, in
which case the RAD approach wins out.
Somewhere along the way y
Most of our code is RAD based (on top of the BDE), but I'm starting to
refactor small pieces of it into testable objects, there is probably
100k lines of "legacy code" that I'm maintaining and I'm finding it too
significant to manage in any reliable way. I've been studying up a bit
and that's
Either really.
Alister Christie
Computers for People
Ph: 04 471 1849 Fax: 04 471 1266
http://www.salespartner.co.nz
PO Box 13085
Johnsonville
Wellington
John Davys wrote:
> Are you asking whether people write their own object-relational persistence
> layers (or use a purchased one)?
>
> I have
7;
Subject: Re: [DUG] OO Programming
Well I have heard comments from 2 commercial sites recently from those
maintaining the code that the object structure used was over-engineered for
what the application needed.
John
___
NZ Borland Developers Grou
Alister
I've written an object-relational (or persistence) framework for PHP,
Heres a list of them
http://www.ambysoft.com/essays/persistenceLayer.html#ProductsOther
> Do people on this list put in the effort to write proper object oriented
> code, or write mostly RAD style code, using datase
Are you asking whether people write their own object-relational persistence
layers (or use a purchased one)?
I have seen that done in the past on a couple of projects in a previous
company I worked for but I don't think it was entirely successful - the
complexity required is not cost effective and
Both.
For anything complex we go the OO route. For simple table maintenance
screens, we tend to follow the RAD approach - there is close to zero
code on simple forms due to our supporting OO frameworks that just link
together at design time.
Found that it takes awhile to get a return/leverage on y
Well I have heard comments from 2 commercial sites recently from those
maintaining the code that the object structure used was over-engineered for
what the application needed.
John
___
NZ Borland Developers Group - Delphi mailing list
Post: delphi@del
Proper OO as much as possible (use of different Patterns, etc), although
we've got a good chunk of legacy code, which has been wrapped up in a
more OO manner, so that we can pretend to ignore it.
RAD, no. I've never been convinced that it's a solid platform on which
to build applications (well, a
Good, well thought out OOP code in meaningful objects - at least *I* think
they are good and well though out :o)
Steve
On Tue, Jul 29, 2008 at 5:08 PM, Alister Christie <
[EMAIL PROTECTED]> wrote:
> Do people on this list put in the effort to write proper object oriented
> code, or write mostly
30 matches
Mail list logo
