No, it's a poor use of your best talent. Imagine a publishing company taking their most successful authors and making them do editing; bad idea.
There should be code reviews, but that doesn't mean it's always a Sr. checking a jr's code. Eventually, everyone on the team should be expected to get to the level where they can contribute code with minimal guidance. They go through the three levels of trust:
- None - I want to see every line of code before you check it in.
- Some - Let me know what you're doing and I'll provide feedback
- Most - Go do your job and only ask for help when needed.
Advantages of freeing up your talent:
- focus on design
- involvement in setting up coding standards and enforcement strategies (without manually doing it all themselves)
- tackle the tough coding problems
- provide mentorship (without having approve every line of code0
There are developers interested in a management path who may prefer not to code all day long; leave the others alone.