My senior developers have around almost a decade of experience. They are open-minded to whatever THEY believe is good. They also lack interest in general problem solving and are not interested in learning.
There's also an ego problem along with this. I am poor in arguments and discussions therefore, I get easily pushed even in discussions on matters that I have researched thoroughly. This is primarily for the fact that I open the discussion showing that I might not be completely right hoping to get the words heard. In addition, the discussion often gets overturned with my own words echoed back at me, e.g., "that's what I've been telling you!", "so you understand now.". This also means I don't get credit for matters I proposed. Even when casually reviewing, they respond with "yeah yeah, I know", "was gonna do it.", etc.
Their limited horizon of experience and ego issues, I believe, is hurting the projects we work upon. For example, someone with such experience not having learned about symlinks. We do get stuff done, but one will quickly realize that the models have not been structured properly, making the work done less satisfactory. They're not to get the entire blame but the way things are structured it's tough for someone new like me.
We will be working on a new project soon and I have suggested the use for a native-hybrid app stack but have felt that I might regret this decision. I would love to try a lot of new things such as FP in this, but I don't think it is worthwhile to be teaching them this for reasons aforementioned. This might hurt my freedom to experience and try such things.
My questions here are:
- How do you deal with individuals that are unwilling to credit you for your proposal?
- Do what's best for the job at hand ignoring under-appreciation?