Good question :) That would probably be closer to a "tech lead" but, of course, it all depends on how your team or organization is structured and what arbitrar

Good question :) That would probably be closer to a "tech lead" but, of course, it all depends on how your team or organization is structured and what arbitrary titles you may use. Someone playing the architect role while staying acquainted to the codebase has been the most effective method in my experience. Finding the balance between looking ahead at future work and needs and working with the team is one of the most difficult aspects of being an effective architect -- but if you can strike that balance, you have the makings of a very productive and happy team.