I'm a senior developer and as well as the "coding up software" and "mentoring others" I get involved in a lot of meetings about future direction, how we will carry out the latest strategy, etc.
My problem is that we seem to have a pattern where our architects and lead software people seem to be making decisions about what "new technology" we should work towards, based on things that are current "Buzzwords" in the market, or things they have gaps in their resume but think will be marketable (for themselves) in the future, to take to interviews for other jobs and so on. Rather than what is actually the most appropriate solution for our company.
"Implemented an architectural shift and eventual rollout to 10000 employees of the XYZ software" speaks volumes -- except XYZ wasn't actually the right solution for this company. They are thinking more about what they need to gain/show experience with, rather than the needs of the company.
Should I just suck it up? Bring it up to anyone within the company? Something else?