I have worked with Drupal, wearing many hats since 2007. That equates to the entirety of my professional career since finishing college. In my previous job I worked with the CMS full time doing front end development, configuration, coding, system architecture, infrastructure, deployments and support. I started out working with Drupal 5 and over four years learned to love it from a development perspective. Four years later I moved on and founded iterate.
I am no longer a developer, I haven't built anything with Drupal in two years and never will again. My current role though still involves Drupal, a lot. We advocate and propose the vast majority of web solutions on the platform. Drupal has been the CMS we have used at iterate since we began and remains to be. It has helped us establish ourselves and scale while securing high profile customers working on enjoyable and rewarding projects. I do not envisage a time where Drupal will not be a significant part of the toolkit used by our development team.
My own perspective on Drupal is however different now as I work with it in a different role. This talk will cover some of the obstacles faced by both agency and customer and how they can be overcome. It will also discuss some of the ways Drupal is, has been and will likely continue to be which while may be great for developers may hinder wider adoption of the platform.