Excellent.  Thanks.  I started on a similar path, good to get all "these" potent "fuel", exactly what I desired.

I like the following part too :)  man, sometime I want to shoot myself for not realizing it soon enough :)  no pun intended earnestly.
>The last bit of advice is to realize when you've won -- and stop
>talking!

>I have found it helpful to use a very simple example that anyone can
>understand:
>
><cfquery name="myQuery">...</cfquery>
><cfoutput query=myquery>...</cfoutput>
>
>Query a database and display the results with 2 CF commands-- no
>connections, no nuthin' -- just 2 CF commands. (I usually code the
>entire logic for creating a Department Phone List, ad hoc.  Then I run
>it, and show the results on a web page (using a Laptop containing CF
>and the Examples "Employee" database)
>
>That = Productivity = RAD -- no other language can do that.  Further,
>the advantage holds whether you are Parsing XML, Providing/Consuming
>Web Services, Making HTTP, FTP, LDAP, File system calls -- CF is a
>higher level than the competition -- it just keeps getting
>better/easier.
>
>Oh, BTW, CF code is human-readable, less-cluttered and more
>maintainable than other code -- (I can't read my Pearl code, I can't
>understand my Java code,  and I won't read my ASP/PHP code).
>
>Seriously, whenever faced with this "challenge" I try to show the
>challenger "Them" vs "Us" with a few simple examples of writing "New"
>code.  Then I turn the discussion to code maintenance -- CF's
>self-documenting orientation wins over the competition, hands down.
>
>If you are presenting to executives, this usually will suffice --
>unless someone has a hidden agenda and brings his
>(ASP/PHP/Perl/JSP/Java...) expert to shoot you down -- if you know that
>is coming, you can ask the opponent  to match your ad hoc efforts.
>
>The last bit of advice is to realize when you've won -- and stop
>talking!
>
>HTH
>
>Dick
>On Mar 8, 2004, at 3:45 PM, Chunshen Li (Don) wrote:
>
>>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to