As a Drupal developer of considerable talent you have probably said to yourself, “I want to be an architect.” But, do you really understand what it means to be an architect? How do the responsibilities differ from your current responsibilities as a developer?
Becoming an architect is not an evolution of your role as a developer. It is a distinct change in your career. Your responsibilities will change to be more leadership and business focused. As a key project leader you will help manage the budget, timeline, and scope while being a client advocate to ensure a successful project. So while the technical skills you have acquired to date will be helpful, to be successful you must learn new skills and change your mindset.
I made the change from developer to architect many years ago without a mentor or a resource to guide my journey. It does not have to be that way for you. As the leader of a Drupal practice, I have mentored many developers along their journey.
Join me In this session where I will discuss what I have learned related to:
* What an architect does
* How an architect’s responsibilities differ from a developer’s responsibilities
* What skills an architect needs: leadership, communication, responsibility, broad and deep knowledge of technology, and project management
* Developing a plan to make the transition from developer to architect
Each attendee will come away with an understanding of what a Drupal architect does, what skills are needed to become one, and how to create a plan to get there.
