From Developer to Architect

Transcript

1. Developer to Architect Mark Taylor | Lead Architect
3. About me • Lead Architect at DealTrak for the last year. • Previously Lead Developer, rose through the ranks over the years. • Mix of experience of Design, Development, DevOps, DBA. • I’ve been a developer for over 15 years. • Interested in programming since I had my first computer (C64). • Involved in the technical architecture of projects for the last 5 years. • Organiser of the PHP Yorkshire conference and Leeds PHP meetup.
4. Types of Architect • Software Architect – solutions for one particular system • Solution Architect – solutions for multiple systems • Enterprise Architect – enterprise wide solution
5. Differences vs Developer? • Requirement for a much broader understanding, both from a technology and business domain perspective. • People skills – communicate and collaborate with the business in order to create the best architecture. • Lots and lots of reading, but focus on breadth rather than depth. • No longer focus on writing code, except for R&D, proof of concepts. • More focus on writing technical specifications and documentation. • Ownership – you are responsible for the whole architecture.
6. Why did I become an Architect? • I wanted to be more involved in “the big picture”. • I became more interested in the business domain. • I have a passion for designing systems. • I could see how all the pieces fit together. • My soft skills evolved, particularly communication. • I am analytical, and I have always loved research and learning. • My company and I saw value in using my skills as a dedicated Architect.
7. Tips on becoming an Architect • Gain a strong understanding of how everything fits together • Learn to let go! You will no longer be the developer. • Develop your communication skills, you have to work with everyone e.g. explain technical concepts to Sales team • Love to learn • Have an eye for detail • Keep on top of industry trends relevant to your domain
8. Mark Taylor | @willCodeForAle