Career Advice for Architects

Transcript

1. Trisha Gee (@trisha_gee) Java Champion & Developer Advocate Career Advice

   for Architects

2. Define “Architect”

3. The hardest single part of building a software system is

   deciding precisely what to build. No Silver Bullet: Essence and Accidents of Software Engineering Frederick P. Brooks, Jr.

4. Everyone is an architect these days (Sorry)

5. You

6. Required Skills

7. Asking Questions Listen to the answers!

8. “Good Communication Skills” Talking to computers is the easy bit

9. Adaptability And being open minded

10. Prioritisation And time management

11. Technology Skills I guess

12. Be aware If you perform non-technical activities too well, you

    may be moved into a non-technical role

13. Scaling

14. Pair Programming Mob Programming

15. Code Reviews Code walkthroughs

16. 20% Time But actually use it!

17. Community Support Give back to the community

18. Book Club With feedback sessions

19. Internal Learning Sessions Internal User Groups

20. Conferences User Groups

21. You don’t need to be In Charge to apply these

    Your responsibility as an architect is to share

22. Benefits of Sharing

23. Backup and Redundancy Specialisation and silos are a risk

24. Increase Team Productivity Teach 9 others your skills to be

    10x more productive

25. Retention …and recruitment

26. It helps you to learn …and it makes you look

    great

27. In Summary

28. Your key skills are not technical

29. To scale your skills, share them

30. Sharing makes you Look Good

31. http://bit.ly/careerFP

32. http://bit.ly/careerFP @trisha_gee