"selecting/recommending tools and frameworks, based on what is most valuable for the business and the team" This is so true, I would say it extends to style amongst other things also. Having worked seniors on teams who had to seemingly make problems "worthy" of their skill and time served. For example working on a large OO Monoliths where a senior started to add lots of "clever" functional code. When I started the question the reasoning behind it I got a lot of instant defensive flack off them because "it's a better way" and "I'm arguing against correctness" they didn't seem to want to understand that we had 50 mid level to junior devs who also had to support this who would require a lot of help to read or follow it, thus slowing the entire team. They didn't seem to care for the reasoning of it being better "for the team" to just carry on with the agreed OO standard.
It's not that I thought they were wrong in what they had to say, just there is an appropriate time and a place and being able to make that call is just as if not more important than the style of functionality being added. I find such seniors can be toxic at times. In essence there is more to being a senior than just being a great coder.
It's not that I thought they were wrong in what they had to say, just there is an appropriate time and a place and being able to make that call is just as if not more important than the style of functionality being added. I find such seniors can be toxic at times. In essence there is more to being a senior than just being a great coder.