Honestly, if your position is that you can't do something; you aren't going to get far with most technical leadership. Even more so, they may immediately question your commitment to your role. A more effective starting position might be that you can do anything, and go from there.
Here's some questions to consider...
Is there a business case to be made for re-building the framework?
How much effort is it to create or implement a replacement framework?
Will the other team members need to be retrained on how to use the new framework? How much time will that take, per person?
Will the current staff be able to manage the new framework going forward?
Will the CI/CD pipelines or code deoployments to production require modification? how much effort is involved in that?
Will you need to create a new database schema to work in the new framework? If so, how much time to create that and migrate the schema during production release?
Will you need to re-write all test cases to work in the new framework? if so, how much time to re-implement them all?
How much time will need to be allocated for QA of the new framework?
How much time will need to be allocated to complete security and performance auditing on the new framework?
How do you release the new project? How will you measure KPI's? How will you roll back? and how much time and effort are all those answers?
... there's plenty more questions to ask yourself, but i'm running out of time.
There is absolutely nothing wrong with pushing for refactoring of existing software; however there are many concerns that get red flagged when the question of new framework / core code base arises. Just make sure you do them for the reasons that can be supported by facts and that help the business. Also you should only work on it when you have the most practical use of that effort, and you have buy in from management and the development team.
Based on the input provided, I would say it would be more prudent for you to push through and learn the current framework it in and out. This is based on you being a new employee, the framework being used for all products/projects, that you only spent a few hours looking through it, and that you have no more questions.
I like to always have the mindset of: always be asking questions. If you ran out of questions to ask then you haven't learned the framework. If you have questions left, keep asking and keep digging for the answers, which will raise more questions. (questions can be to yourself, like how the hell does this work?...then go find out). You could always start a small demo service using the framework as a way to get more comfortable with it.
Honestly, if your position is that you can't do something; you aren't going to get far with most technical leadership. Even more so, they may immediately question your commitment to your role. A more effective starting position might be that you can do anything, and go from there.
Here's some questions to consider...
There is absolutely nothing wrong with pushing for refactoring of existing software; however there are many concerns that get red flagged when the question of new framework / core code base arises. Just make sure you do them for the reasons that can be supported by facts and that help the business. Also you should only work on it when you have the most practical use of that effort, and you have buy in from management and the development team.
Based on the input provided, I would say it would be more prudent for you to push through and learn the current framework it in and out. This is based on you being a new employee, the framework being used for all products/projects, that you only spent a few hours looking through it, and that you have no more questions.
I like to always have the mindset of: always be asking questions. If you ran out of questions to ask then you haven't learned the framework. If you have questions left, keep asking and keep digging for the answers, which will raise more questions. (questions can be to yourself, like how the hell does this work?...then go find out). You could always start a small demo service using the framework as a way to get more comfortable with it.
good luck.
Consulted with other team members and we have collectively agreed to migrate to a new framework soon.
nice! Congrats and I wish you and your team good fortune in your journey into a new framework at your job.
which framework did your team choose?