<div dir="ltr">"cunning bastard" - must have that printed on my cards.<br><br>Must be something to do with age as they say that "Wisdom comes with age". But someone once told me that "Sometimes age comes all on its own". I find it never pays to ask if that's happened with me :o)<br>
<br>As for the "Software Architect" title that started this thread (it all eventually runs in a full circle). That is normally someone who knows an ERP system (e.g. SAP / PeopleSoft / Microsoft Dynamics Navision / JD Edwards / et el.) so well that they can design the interfaces between the various ERP components and external functionality in big diagrams on a whiteboard.<br>
<br>Essentially however, I much prefer the description given earlier that corresponds to the "What is an expert" description - someone brought in from another city and wearing a suit and carrying a briefcase.<br>
<br>Steve<br><a href="http://stevepeacocke.blogspot.com/" target="_blank">http://stevepeacocke.blogspot.com/</a><br><br><br><div class="gmail_quote">On Wed, Jul 30, 2008 at 10:24 AM, Neven MacEwan <span dir="ltr"><<a href="mailto:neven@mwk.co.nz">neven@mwk.co.nz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Steve<br>
<br>
Thats because your a cunning bastard that has worked out telling the<br>
masses its easy never pays..<br>
<br>
This is appropo to the Software Architect Question...whatr the f%k is a<br>
Software Architect?<br>
Sounds like a title looking for a salary<br>
<br>
Neven<br>
<div class="Ih2E3d"><br>
<br>
> Its never "that other 5%". My favourite saying is explaining that the<br>
> main problem with most programming is that last little wee 95%.<br>
><br>
> :o)<br>
><br>
> Steve<br>
> <a href="http://stevepeacocke.blogspot.com/" target="_blank">http://stevepeacocke.blogspot.com/</a><br>
><br>
> On Wed, Jul 30, 2008 at 10:08 AM, Neven MacEwan <<a href="mailto:neven@mwk.co.nz">neven@mwk.co.nz</a><br>
</div><div><div></div><div class="Wj3C7c">> <mailto:<a href="mailto:neven@mwk.co.nz">neven@mwk.co.nz</a>>> wrote:<br>
><br>
> Steve<br>
><br>
> So what we need is OO RAD? Where you define classes and they<br>
> 'instantly'<br>
> appear on your palette (and are dynamically updated)<br>
> And a O-R framework is part of the language?<br>
><br>
> The problem has been of course that the Table Row = Business<br>
> Object is a<br>
> 95% accurate solution and so the Delphi IDE<br>
> has basically delivered in 95% of situations<br>
><br>
> That other 5% is a bastard though<br>
><br>
> Just a thought<br>
> Neven<br>
> > Yea, thanks Conor,<br>
> ><br>
> > Sure, in RAD, as it is in any Delphi project, you can certainly get<br>
> > away with simply programming the event handlers in the components<br>
> > (depending on the application). That should not preclude being<br>
> able to<br>
> > create, for example, an Application Object that handles all your<br>
> > globals like the logged in user, or the company name and other<br>
> details<br>
> > needed at times (e.g.; lbCompany.Caption := oApp.CompanyName) -<br>
> where<br>
> > perhaps the company name is extracted from the database etc. In this<br>
> > example, oApp knows how to extract the company name, and perhaps<br>
> even<br>
> > format it for display.<br>
> ><br>
> > RAD does not mean ShiteProgramming, or NoThoughtProgramming. Its<br>
> hard<br>
> > to find a definitive definition (?) for RAD and a quick search shows<br>
> > various descriptions from the tool itself (Delphi or VB) to the<br>
> whole<br>
> > spectrum of Agile methodologies.<br>
> ><br>
> > However, I do disagree with the assertion that RAD does not lend<br>
> > itself to larger apps (or did you mean "Rapid Prototyping"). In fact<br>
> > RAD is an excellent development environment for developing even<br>
> > enterprise level applications. Some years ago I had the pleasure of<br>
> > working in a team of between 3-5 developers where we used a RAD<br>
> > approach (using Delphi) in an iterative and incremental development<br>
> > methodology to produce a very large scale corporate application and<br>
> > can confirm the approach as excellent and the development far<br>
> > outperforms a team up to 10 times larger using Java/J2EE in a<br>
> refined<br>
> > waterfall approach for a similar sized project.<br>
> ><br>
> > Steve<br>
> ><br>
> > On Wed, Jul 30, 2008 at 8:27 AM, Conor Boyd<br>
> <<a href="mailto:Conor.Boyd@trimble.co.nz">Conor.Boyd@trimble.co.nz</a> <mailto:<a href="mailto:Conor.Boyd@trimble.co.nz">Conor.Boyd@trimble.co.nz</a>><br>
> > <mailto:<a href="mailto:Conor.Boyd@trimble.co.nz">Conor.Boyd@trimble.co.nz</a><br>
> <mailto:<a href="mailto:Conor.Boyd@trimble.co.nz">Conor.Boyd@trimble.co.nz</a>>>> wrote:<br>
> ><br>
> > Probably because I don't put the acronym RAD and the word<br>
> > "programming" together as you have done.<br>
> ><br>
> > From my POV, RAD is generally taken to mean what the acronym<br>
> > stands for, Rapid Application Development; i.e. drop some<br>
> > components on to a form, wire up a few event handlers, voila.<br>
> ><br>
> > Doesn't mean I don't "do" OOP in event handlers and the little<br>
> > amount of code that is required in such an app, but IMHO you're<br>
> > comparing apples with oranges.<br>
> ><br>
> > RAD does not lend itself to larger apps which are intended to be<br>
> > easily maintainable and intended to be worked on by a team of<br>
> > developers.<br>
> ><br>
> > Cheers,<br>
> ><br>
> > C.<br>
> ><br>
> ><br>
> ------------------------------------------------------------------------<br>
> > *From:* <a href="mailto:delphi-bounces@delphi.org.nz">delphi-bounces@delphi.org.nz</a><br>
> <mailto:<a href="mailto:delphi-bounces@delphi.org.nz">delphi-bounces@delphi.org.nz</a>><br>
> > <mailto:<a href="mailto:delphi-bounces@delphi.org.nz">delphi-bounces@delphi.org.nz</a><br>
> <mailto:<a href="mailto:delphi-bounces@delphi.org.nz">delphi-bounces@delphi.org.nz</a>>><br>
</div></div>> > [mailto:<a href="mailto:delphi-bounces@delphi.org.nz">delphi-bounces@delphi.org.nz</a><br>
<div class="Ih2E3d">> <mailto:<a href="mailto:delphi-bounces@delphi.org.nz">delphi-bounces@delphi.org.nz</a>><br>
> > <mailto:<a href="mailto:delphi-bounces@delphi.org.nz">delphi-bounces@delphi.org.nz</a><br>
> <mailto:<a href="mailto:delphi-bounces@delphi.org.nz">delphi-bounces@delphi.org.nz</a>>>] *On Behalf Of *Steve Peacocke<br>
> > *Sent:* Wednesday, 30 July 2008 8:13 a.m.<br>
> > *To:* NZ Borland Developers Group - Delphi List<br>
> > *Subject:* Re: [DUG] OO Programming<br>
> ><br>
> > Just an interesting observation - why do people think that RAD<br>
> > programming excludes OOP programming?<br>
> ><br>
> > RAD is a methodology, OOP is a programming style.<br>
> ><br>
> > Steve<br>
> > <a href="http://stevepeacocke.blogspot.com/" target="_blank">http://stevepeacocke.blogspot.com/</a><br>
> ><br>
> > _______________________________________________<br>
> > NZ Borland Developers Group - Delphi mailing list<br>
> > Post: <a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a> <mailto:<a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a>><br>
</div>> <mailto:<a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a> <mailto:<a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a>>><br>
<div><div></div><div class="Wj3C7c">> > Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
> > Unsubscribe: send an email to <a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a><br>
> <mailto:<a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a>><br>
> > <mailto:<a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a><br>
> <mailto:<a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a>>> with Subject: unsubscribe<br>
> ><br>
> ><br>
> ><br>
> ------------------------------------------------------------------------<br>
> ><br>
> > _______________________________________________<br>
> > NZ Borland Developers Group - Delphi mailing list<br>
> > Post: <a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a> <mailto:<a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a>><br>
> > Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
> > Unsubscribe: send an email to <a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a><br>
> <mailto:<a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a>> with Subject: unsubscribe<br>
><br>
> _______________________________________________<br>
> NZ Borland Developers Group - Delphi mailing list<br>
> Post: <a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a> <mailto:<a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a>><br>
> Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
> Unsubscribe: send an email to <a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a><br>
> <mailto:<a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a>> with Subject: unsubscribe<br>
><br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> NZ Borland Developers Group - Delphi mailing list<br>
> Post: <a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a><br>
> Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
> Unsubscribe: send an email to <a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a> with Subject: unsubscribe<br>
<br>
_______________________________________________<br>
NZ Borland Developers Group - Delphi mailing list<br>
Post: <a href="mailto:delphi@delphi.org.nz">delphi@delphi.org.nz</a><br>
Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
Unsubscribe: send an email to <a href="mailto:delphi-request@delphi.org.nz">delphi-request@delphi.org.nz</a> with Subject: unsubscribe<br>
</div></div></blockquote></div><br></div>