This question already has an answer here:
Where I'm working, the developers changed every year, with each developer leaving his own way of doing things, and moving on afterwards, the code-base lacks proper documentation, is not developed with performance, or ease of migration, upgrade in mind, only focused on developing new features and fixing bugs.
Which puts me in an awkward position, the CTO changed once, and the current CTO is oldest one around the code base, if I have anything in mind to present or suggest it has to go through him, I thought of many things that could help from my point of view, but been holding back since the beginning of my employment out of fear that my ideas would seem far apart from the CTO's mind set or way of doing things.
How would anyone suggest a proper, and well thought approach of addressing this, my objective is to actually migrate the code-base from nodejs 4 to nodejs 6, rework the application architecture, and introduce nosql database, and maybe in the future migrate to micro-service architecture.
What I'm looking for is how to approach my CTO with a lets come together as a team and build scalable and new tech system upon the old attitude, As I intend to be there during the migration, and see this company step from one position to the next.