Maybe something missing. Reusable Component such as record locking mechanism, report printing, form validation, grid table, pop up window, error handling, notification.
All of reusable component that could be used.
Also, base class that developer can be extended. They just need to focus business logic instead of whole work.
If the code is split into modules, libraries and such, as reusable components, the "framework" will naturally evolve over time, if the code is shared between teams/products.
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.
Just for the application in order to make the developer follow same structure, coding standards, flow behaviour, auto some task (code generation)
That does not sounds like a framework, those jobs can be applied at IDE level, CI/CD pipelines.
Maybe something missing. Reusable Component such as record locking mechanism, report printing, form validation, grid table, pop up window, error handling, notification.
All of reusable component that could be used.
Also, base class that developer can be extended. They just need to focus business logic instead of whole work.
I think I understand now, yes so ..
If the code is split into modules, libraries and such, as reusable components, the "framework" will naturally evolve over time, if the code is shared between teams/products.