My programming path has gone from "hobbyist game developer" (C, C++ circa 1994/5) through to regular developer up to ~2001 (mostly vb6) , then .net developer with SQL server/data access focus for a couple of years, into pretty much full time (90%+) SQL developer/DBA/code reviewer for the last 8 - 10 years.

Aside: I'm still not entirely sure I understand the term "DBA". Some people take it to mean simply those who know how to keep the backups running and monitor server health, others take it to mean someone who can do this stuff but also knows TSQL inside-out, understands the intricacies of the technology, and so on - ie, more of a lead developer.

I was drawn away from regular application programming over to the SQL side by the more robust arguments for "good design" (ie, based on set theory) than the sometimes-merely-opinion arguments as to what constitutes good design on the "application code" side, and I'm a sucker for predicate logic. (Also I hate web development 😛 )

For the last couple of years I have naturally moved into software architecture, enterprise architecture and (in particular) information architecture space. The information architecture connection is obvious enough, the others may not be so clear but the connection comes from the fact that just about everything in an enterprise touches something the DBA has an eye on, so you get to know the overall software landscape better than just about anyone. This includes noticing where there are architectural conflicts and so on (if you are interested in that kind of thing).

I have absolutely no interest in management. I don't think I'll ever shake the "SQL DBA" side though