This is a good article. I was an Oracle Developer 10 years ago and then a company hired me as a SQL Server developer. The manager and I both thought SQL was SQL, what's the difference? Of course we were both wrong. I also interviewed with the DBA of that company at that time, he seemed to be a nice guy. After I started the job, I found out SQL Server developer was totally different. The DBA was a very knowlegable guy but he was rude, unprofessional and yelled at you liked you were a garbage. Since I was new at SQL server, I asked a question. His answer was ' Look at BOL, I don't have time to answer all the stupid questions'. Whatever you did , you had to do his way or no way. You were not allowed to create, you had to follow his instructions. The manager was totally on his side because she had no clue about database, she was totally relied on him. They hired another DBA who argued with him, the result the new DBA was fired.
This was an article about DBA job. Basically I had to do all of them except installing SQL Server and disaster recovering. I had to say I learnt a lot but after two years of mentally abusing, I had to quit because I was at the edge of a nervous break down.
After I found another job as SQL Server programmer, I found out I did a lot of the DBA work. I even knew more than the DBA of that company (it was a little pathetic.) This was due to two years of SQL Server boot camp.
But my point is the DBA's attitude is very important too. That company’s developer turnover rate was very high probably because of the DBA’s abuse. Knowledge is important, you have to hire someone knowing how to do the job but at the same time you have to find someone that can fit into your company and can work with other people.