Trisha Gee (@trisha_gee)
Java Champion & Developer Advocate
Career Advice
for Architects
Slide 2
Slide 2 text
Define “Architect”
Slide 3
Slide 3 text
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.
Slide 4
Slide 4 text
Everyone is an architect these days
(Sorry)
Slide 5
Slide 5 text
You
Slide 6
Slide 6 text
Required Skills
Slide 7
Slide 7 text
Asking Questions
Listen to the answers!
Slide 8
Slide 8 text
“Good Communication Skills”
Talking to computers is the easy bit
Slide 9
Slide 9 text
Adaptability
And being open minded
Slide 10
Slide 10 text
Prioritisation
And time management
Slide 11
Slide 11 text
Technology Skills
I guess
Slide 12
Slide 12 text
Be aware
If you perform non-technical activities too well, you may
be moved into a non-technical role
Slide 13
Slide 13 text
Scaling
Slide 14
Slide 14 text
Pair Programming
Mob Programming
Slide 15
Slide 15 text
Code Reviews
Code walkthroughs
Slide 16
Slide 16 text
20% Time
But actually use it!
Slide 17
Slide 17 text
Community Support
Give back to the community
Slide 18
Slide 18 text
Book Club
With feedback sessions
Slide 19
Slide 19 text
Internal Learning Sessions
Internal User Groups
Slide 20
Slide 20 text
Conferences
User Groups
Slide 21
Slide 21 text
You don’t need to be In Charge to
apply these
Your responsibility as an architect is to share
Slide 22
Slide 22 text
Benefits of Sharing
Slide 23
Slide 23 text
Backup and Redundancy
Specialisation and silos are a risk
Slide 24
Slide 24 text
Increase Team Productivity
Teach 9 others your skills to be 10x more productive
Slide 25
Slide 25 text
Retention
…and recruitment
Slide 26
Slide 26 text
It helps you to learn
…and it makes you look great