As a database/web developer for over 16 years, I completely agree with the idea of cross training when it comes to developers and DBAs. Doing so gives each a better perspective on what the other does as well as making it more efficient to troubleshoot developmental issues that might be related to either the database end or the application calling the database. I have always thought a developer should know more about the DBA side so that if a problem comes up that "appears" to be a problem that has to be resolved by the DBA, the developer can point the DBA in the right direction to troubleshoot. This is of course reversed when the two put their heads together and the DBA points the developer to the right place to look in their code for the problem. Part of the reason I do this is because I want the problem solved asap and part of it is because I figure the DBA is extremely busy and if I point him in the right place to look in the database that will save him time in rectifying the problem.