This is a very interesting question. Having been both a developer and now a DBA, I can see the arguement from both sides of the fence as well as the different pressures and requirements each job has. It is important to remember that we all have the same end goal. Fast, reliable, useful applications.

A short answer: beer. Go for a drink with the other team. Become people to each other. Learn why developers often rush out bad code thinking that we will fix in the next release. Learn why DBAs have to balance security, effciency, troubleshooting SQL code becauase every thing ends in a database, whilst keeping an eye on the detail and the bigger picture at the same time.

The long answer is much more complicated. However, I feel that the important thing for a DBA to remember is that we, as most of us who are in IT, are a support role. We support the databases, the data integrity, the developers (support them to write better SQL code) and the businesses we all work for. There are many ways in the SQL world to do a thing and sometimes someone elses way may be better than yours. We all have the same end goal, developers and DBA's alike. No one wants a slow unreliable application. Good luck everybody.