I would also point out that it is impossible as a salaried employee to convince most managers of anything without a personal relationship. They tend to view any sort of course change as a personal failure that will reflect badly on them so you are going to need that trust and political capital beforehand. This is especially true if you are new to the company. No one wants the new engineer to come in and quickly point out where things are going wrong.
A company should want the new engineer to come in and quickly point out where things are "not that obvious" to him/her.
The point is, and this is the hard part and mostly underdeveloped area: use the soft skills to put the point across. Be humble, ask questions, play "dumb" (uninformed). Repeat the available information, rephrase it, ask a question and most often than not the silliness, the absurdity of the reasoning behind decisions become apparent. And this all by just stating facts, not mumbling opinion. It's a technique which you can apply everywhere, not only in the programming world.
At the current company I work for, the state of the codebase was already obvious. People acknowledge it, own it. Good. But even though I started in March 2022, this year, I am able to make suggestions, pose proof of concepts for the betterment or at least ponder about approaches that might be useful. Now, or later on. Posing myself as wanting to bring value and improvement is highly welcomed. Just don't be cocky, arrogant, rude, aggressive or mean. Nobody wants such a (new) member on the team.
Packaging the bad news is a highly valued skill to possess.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would also point out that it is impossible as a salaried employee to convince most managers of anything without a personal relationship. They tend to view any sort of course change as a personal failure that will reflect badly on them so you are going to need that trust and political capital beforehand. This is especially true if you are new to the company. No one wants the new engineer to come in and quickly point out where things are going wrong.
A company should want the new engineer to come in and quickly point out where things are "not that obvious" to him/her.
The point is, and this is the hard part and mostly underdeveloped area: use the soft skills to put the point across. Be humble, ask questions, play "dumb" (uninformed). Repeat the available information, rephrase it, ask a question and most often than not the silliness, the absurdity of the reasoning behind decisions become apparent. And this all by just stating facts, not mumbling opinion. It's a technique which you can apply everywhere, not only in the programming world.
At the current company I work for, the state of the codebase was already obvious. People acknowledge it, own it. Good. But even though I started in March 2022, this year, I am able to make suggestions, pose proof of concepts for the betterment or at least ponder about approaches that might be useful. Now, or later on. Posing myself as wanting to bring value and improvement is highly welcomed. Just don't be cocky, arrogant, rude, aggressive or mean. Nobody wants such a (new) member on the team.
Packaging the bad news is a highly valued skill to possess.