So I am less than a month in to a wonderful new job and I will get right to the point. From day one the CTO has told me to please poke holes and look for inconsistencies and what needs improvement.
On my first and second week, it was too early to find any, but on my third week I have found something.
Well, now I am meeting with the Senior Developer more so than the CTO and so I brought these inconsistencies up with him.
The response I get is, well, the client is not worried about that and we are moving away from that technology anyways.
The piece that I need to also disclose is that its a piece of technology I have spent countless hours mastering and also implementing in other companies and for other customers and so the philosophy that we are replacing it with something better and new falls short of the fact that its not going to completely go away so it behooves us to all learn it, especially for devs that come after me.
Anyway, my question is, what is the best way to address this in a way that I safeguard myself as the new guy and I am not throwing the Senior Dev under the bus?
I could have made the argument and may possibly still have the chance to make the argument to the Senior Dev, that it affects my productivity when I look at a codebase that is unnecessarily disorganized and snippets of code here and there implemented in the past that for someone of my experience, I know are not providing any improved quality to the product.
How do I communicate my concerns?