One of the difficult tasks an architect faces is how to balance hands-on coding with

software architecture. 

Every architect should code and be able to maintain a certain level of technical depth

• The bottleneck trap occurs when the architect has taken ownership of code within the

critical path of a project (usually the underlying framework code) and becomes a

bottleneck to the team. 

This happens because the architect is not a full-time developer and therefore must balance between playing the developer role

• One way to avoid the bottleneck trap as an effective software architect is to

delegate the critical path and framework code to others on the development team

and then focus on coding a piece of business functionality (a service or a screen) one

to three iterations down the road.

https://medium.com/@biancamagri/summary-chap-2-fundamentals-of-software-architecture-ec4532901285