Cart
[Home] [By Thread] [By Date] [Recent Entries]
Actually, that is what you have to do. o Use what they publish if useful (eg, extract the elements out of the data dictionary). o Ignore things that are nonsense on the face of it (eg, directives to avoid use of attributes). o Train yourself by research and experimentation (The Didier Method) but do not ignore the library (a day in the library is worth a month in the lab). o Eventually you have to code. Trust yourself to do that well. o Don't let RFPs be something only the marketing group sees. They have views you don't have. o Don't go silent about designs if the marketing group is in earshot. They have views you don't have. o Tomorrow is another day. Versions are there because nothing is done completely up front. Make sure the proposal is clear about that because it is money off the table and in the bag. o Do what makes sense to you. Otherwise, nothing will make sense. If you lose from ignorance, that is a chance to learn. If you lose from hubris, that is a chance to be fired. len -----Original Message----- From: Mike Champion [mailto:mc@x...] I presume that "do something sensible to get local agreements and let the global standards bodies fight" is not a viable option ... or is that wrong?
|
