100% inclined to agree. DevOps is not really about your best and brightest pure programmers, but taking all of your jack-of-all-trades guys who specialize in "making shit work" and allowing them to keep things working.
There is a conflict in the role of a DevOp though that you need to understand. In the Dev role you will be working on a project and to a deadline, and will just want to make "ad hoc" changes as needed for your application to work. As an Op role you have to say "hold on, lets make sure all those system tweeks have no other impact, apply them via reproducible deployment scripts, and maybe go back and take another look at your hooks into the alerting/monitoring system". As long as you and your boss understand that everything is fine - if not more and more of your time will end up firefighting in the "ops" role.