John Farrar: "With talk like that you will likely make the "do not hire list"... heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh, heh .... whew, better get refocused. (Couldn't resist, and maybe this will guarantee me a slot on the list also. Yet... someone said something about if your not annoying someone you're not doing anything worth while.)"
LOL. I know exactly who you're referring to. You'd better watch out, because he has a lot of contacts in the industry. If you are on his do not hire list, you most assuredly won't get a job, ANYWHERE! ;) John Farrar: "Hey... the big question is not how long it's going to take you on a lifecycle use of your work. If it's not going to be reused or shared with others then you may have the better choice. There is risk in both directions and many guys will argue the safe bet is to make it all scale and use perfect design according to our current understanding. Yet, as you said... there comes a time when that isn't a 100 percent rule. There is a point where we need to not be so "productive" to make ourselves look good now that we don't honestly evaluate the lifecycle effect of our immediate time savings. I have learned a good deal from this list on that topic on this list, even if I draw the line differently than the social safe list location personally. So if you have, or anyone else made a responsible choice on that type of thing... you may be through repeated choices of right selections saving lotsa moola! Only time and experience will tell how well you, I or anyone else does at making those choices." I think you make an excellent point: It depends. :) I am a big fan of code reuse, and ease of maintainability. Don't get me wrong. If you all saw my coding style, you'd have to agree that I am not a spaghetti coder. However, I strongly believe that most of the time its better to get a job done and move on the next big money project, than to spend days and days making sure I have all the dao's and gateways properly behaving. It is totally possible to code using basic OO principles, while rapidly developing and application (there's that RAD term again). I think you can have more clients satisfied (or bosses in my case) in a shorter period of time, make a lot more money, AND get the hot girl in the end. ;) This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. A1. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
