Remember who you're audience is. He is a programmer who thinks in precedural terms.
He probably scoffs at scripting languages (which is what CF feels like). He is probably a little intimidated with OOP. You are not easily going to change his basic underlying prejudice towards his development environment, so you are going to need to speak in terms he can easily and comfortably grasp. Procedure. Function. Compile. Warning. Error. Library. Include. Global and local variable. Application. Variable types. Then and only then can you start throwing in extra info like CFCs, objects, Java, custom tags. If he can grasp that he already has the skills (although not the syntax) to develop in CF, and if he can make the conversions in his head between what he knows and what you are doing. Also, stress the ease of prototyping, and the ease of separating coding from display from content (so that the client and non-programmers (read cheap labor) can have a larger hand in the site creation). And finally, let him know that it needn't be all-or-nothing. If he goes your route, with CF in the mix, he can STILL develop certain pages, or leave legacy code in php, yet have all the benefits of CF when fast, clean code needs to be developed in a short time. Jerry Johnson ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:227570 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
