> paper on architecture and development? Where's your best practices piece? > I'm not trying to be a prick, I'm trying to say two things basically: > I have written plenty of these documents. Just because they are not in the public space doesn't change anything. You might be surprised at the number of these documents in existence that never leave a company because of IP issues. Just FYI, when you are an application architect you have to write these documents.
> way of doing something it does? I would be happy to hear it. > I mean this in the nicest possible way... you are out of your league here. It's not like you can pick apart specific details. Fusebox simply doesn't address important issues. Tell you what, if you agree to sign an NDA, I will show you all kinds of wonderful specifications and actual code for some top notch architectures and frameworks. > 2. I guess this also ties into part one. Practice what you preach. You > don't think Hal and Steve and all the rest are dong something that is good > for coders? Do something better. Send in some links, something besides > complain. > Again, I can't because of IP issues. All I can do at this point is show where they are lacking. -Matt ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
