[kotxig]

I understand what you're saying. What I was trying to illustrate was that by virtue of knowing the ins and outs of the codebase, it's easy for them to make changes (hence the quotes around "super effective"). It would be impossible to conceive or design a non-trivial feature without their input. For me it feels absolutely necessary to get to the point where I could effectively design end to end features without their input.

I'm not convinced that leaving right now is the only solution, hence the question. If your answer to the question is "you don't, just leave" then that's fine, but I am hoping there are other strategies that I can personally bring to the table to make this team more effective.

[throwaway-7494]

My answer isn't "you don't, just leave". My answer is that programming and effective engineering is a team sport. Not asking for input and feedback is counter-intuitive for me and frankly is a form of machismo that I would rather avoid. I'm not an effective engineer because I can ship code 24 / 7, I'm an effective engineer because I can transfer and translate business requirements into code and effectively communicate the semantics of the code to others contextualized with the business requirements that lead to the creation of the code.