One of the long running arguments in the development community is how much SQL code developers should be writing, as opposed to letting a DBA handle it. In addition, many tools now reduce or even eliminate the amount of SQL that developers write. And, there are some programmers who do not use SQL at all.
I've had jobs where being a "developer" simply meant "put a nice UI on top of a ton of SQL you write," and I've had jobs where I didn't go anywhere near a database. Tell us whether you're writing a lot of SQL in your current job.
Justin James is the Lead Architect for Conigent.