This can be re-written almost as "the development of the young programmer" where the external forces exert themselves and you get forced into some of the roles.

This can be re-written almost as "the development of the young programmer" where the external forces exert themselves and you get forced into some of the roles... - sometimes the pressure is speed of project completion - sometimes the pressure is production quality - sometimes the pressure is code quality / reusability - sometimes the pressure is following specs - sometimes the pressure is "looking modern" - sometimes the culture is whack and needs to be changed - sometimes the pressure is team communication - sometimes your tech stack only includes an AS400 Whatever the pressure you can seemingly get pidgeon-holed. I think this is where experience comes in and can guide you to the happy medium where external pressures are ignored and you balance the best you can.