> Nitpicking over "not my specialization" is the antithesis of a smooth engineering process. Counter argument: jack of all trades, master of none. I'm already

> Nitpicking over "not my specialization" is the antithesis of a smooth engineering process. Counter argument: jack of all trades, master of none. I'm already a full stack developer. I work on a complex front end application, a GraphQL server, a .net core platform split into multiple microservices, and a MSSQL database. I know my way around these components fairly well now but it's taken a good couple of years to get to this point. I could also invest a bunch of my time learning all the intricacies of cloudformation templates and how IAM roles work too, sure. But is it the best use of my time as a developer, when I'm much more productive writing code? You can just end up stretched too thin.