I'm ops, but the cool thing about ansible is that it is easy to get devs to help. They know their software packages, I don't, but I can point them at a playbook and they can fairly easily fill out the basics, I can work on the orchestration after they have done the initial playbook design and testing.
Chef (and formerly Puppet) had (for us) a much higher barrier to entry when it comes to getting an unfamiliar dev on board. We basically had to get reqs from the dev, and then we would build the recipes.
From surveys we've done, I think the breakdown is about 60% on the ops side, 40% on the developer side. Obviously in a lot of startups, especially folks using cloud stuff, lines blur a lot.
I wanted to make a language that was good for both, and easy to do ordered tasks, and a lot of app deployment requires ordered tasks and being able to do things on the result of other things. OTOH, sysadmins want a language that is easy to read and has the declarative state features, so it's kind of both at the same time.
